than just showing the incomprehensible formulas.

that are almost never used.  Put documentation-related variables into the
documentation chapter.

This was required back when RESUME_INTERRUPTS could actually
execute ProcessInterrupts, but that hasn't been true since 2001...

newlines.

because the function didn't exist in 7.4.X.

Marko Kreen

>   http://archives.postgresql.org/pgsql-hackers/2006-10/msg00820.php

the politically correct view that backslash escapes are deprecated.

scenarios. With multiple clinets, only the first client got the right
scaling factor and this gave a illusion of better performance in case
of the scaling factor greater than 1.

and avoid scribbling on its result (might be safe but why risk it)

Going to wait for buildfarm results before backpatching, this time.

Remove obsolete note about logging of statements generated by plpgsql
function execution ... that doesn't happen anymore.

a fastpath function call.

provide a macro so code can still just say qsort).  Avoids linker warnings
on pickier platforms such as Darwin, and outright failure on MSVC.

instead of inserting an MSVC dependency.

< * Improve port/qsort() to handle sorts with 50% unique and 50% duplicate
<   value [qsort]
<
<   This involves choosing better pivot points for the quicksort.
<

be NULL ... seems an unsafe assumption.

if available (which it usually should be), during processing of Bind
and Execute protocol messages.  This improves usefulness of
log_min_error_statement logging for extended query protocol.

from Magnus that MSVC complains about this.

per Magnus.

sin_port in the returned IP address struct when servname is NULL.  This has
been observed to cause failure to bind the stats collection socket, and
could perhaps cause other issues too.  Per reports from Brad Nicholson
and Chris Browne.

that conflict with the OID that we want to use for the new database.
This avoids the risk of trying to remove files that maybe we shouldn't
remove.  Per gripe from Jon Lapham and subsequent discussion of 27-Sep.

timezone actually has a daylight-savings rule.  This avoids breaking
cases that used to work because they went through the DecodePosixTimezone
code path.  Per contrib regression failures (mea culpa for not running
those yesterday...).  Also document the already-applied change to allow
GMT offsets up to 14 hours.