declared in the system headers.  Per report from Bruce than some BSDen
are like this.

which turns out to be a dominant part of the runtime in scenarios
involving lots of parse-time warnings (such as Stephen Frost's example
of an INSERT with a lot of backslash-containing strings).  There's not
a whole lot we can do about the character-at-a-time scanning, but we
can at least avoid traversing the query twice.

severity.  This is to ensure the user can cancel a query that's spitting
out lots of notice/warning messages, even if they're coming from a loop
that doesn't otherwise contain a CHECK_FOR_INTERRUPTS.  Per gripe from
Stephen Frost.

file is read with an incompatible client_encoding setting.  Per report
from Tim N. van der Leeuw.

CaseTestExpr, but forgot that the optimizer is sometimes able to replace
CaseTestExpr by Const.

work around that with defines.

> * Allow more complex user/database default GUC settings
>   Currently, ALTER USER and ALTER DATABASE support per-user and
>   per-database defaults.  Consider adding per-user-and-database
>   defaults so things like search_path can be defaulted for a
>   specific user connecting to a specific database.
>
>

>   http://archives.postgresql.org/pgsql-hackers/2006-09/msg01107.php

present; intervening positions are filled with nulls.  This behavior
is required by SQL99 but was not implementable before 8.2 due to lack
of support for nulls in arrays.  I have only made it work for the
one-dimensional case, which is all that SQL99 requires.  It seems quite
complex to get it right in higher dimensions, and since we never allowed
extension at all in higher dimensions, I think that must count as a
future feature addition not a bug fix.

NULL.  Noted by Teodor.

the SQL spec, viz IS NULL is true if all the row's fields are null, IS NOT
NULL is true if all the row's fields are not null.  The former coding got
this right for a limited number of cases with IS NULL (ie, those where it
could disassemble a ROW constructor at parse time), but was entirely wrong
for IS NOT NULL.  Per report from Teodor.

I desisted from changing the behavior for arrays, since on closer inspection
it's not clear that there's any support for that in the SQL spec.  This
probably needs more consideration.

>   http://archives.postgresql.org/pgsql-hackers/2006-08/msg01696.php

explicitly.

to performance.  (A wholesale effort to get rid of strncpy should be
undertaken sometime, but not during beta.)  This commit also fixes dynahash.c
to correctly truncate overlength string keys for hashtables, so that its
callers don't have to anymore.

available directly on the platform.  Per discussion, this function is
sufficiently widely recognized to be treated as standard.

spelled with a capital "I".

discussion.

Patch from Simon Riggs.

< 	  o Add command to archive partially filled write-ahead logs? [pitr]
<
< 	    Currently only full WAL files are archived. This means that the
< 	    most recent transactions aren't available for recovery in case
< 	    of a disk failure.
<

Reorder:

< 	  o %Create dump tool for write-ahead logs for use in determining
< 	    transaction id for point-in-time recovery
> 	  o %Create dump tool for write-ahead logs for use in determining
> 	    transaction id for point-in-time recovery

Added SET DATESTYLE to one test so the output format is defined.

wrong answer, as has been seen to occur with a buggy Linux kernel.  Not
really our bug, but it's a simple test in a seldom-used control path,
so might as well have a defense.

for DROP AGGREGATE IF EXISTS.  Per report from Teodor.

make fopen work safely on Windows.  Magnus