< 	  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

'postmaster', so as not to depend on the existence of the postmaster
symlink.  Also, implement postmaster-still-alive and postmaster-kill
operations for Windows, per Magnus.

Tag us Beta1

backward compatibility for anyone using the old userlock code that's now
on pgfoundry --- locks from that code still show as 'userlock'.

return true for exactly the characters treated as whitespace by their flex
scanners.  Per report from Victor Snezhko and subsequent investigation.

Also fix a passel of unsafe usages of <ctype.h> functions, that is, ye olde
char-vs-unsigned-char issue.  I won't miss <ctype.h> when we are finally
able to stop using it.

(possibly (un)translated) letters that are actually expected as input.
Also reject invalid responses instead of silenty taken them as "no".

with help from Bernd Helmle

match what SHOW displays as default value, to make the user experience
uniform.

giving tables of known timezone names, refer the user to the system views.
Joachim Wieland

Add URL's to mention proper entity lists.

not in the character set supported by DocBook nor standard HTML.  (Sorry
Volkan.)  Also replace random character-set references by a pointer to
the actual standard.

even when a single relation requires more than max_fsm_pages pages.  Also,
make VACUUM emit a warning in this case, since it likely means that VACUUM
FULL or other drastic corrective measure is needed.  Per reports from Jeff
Frost and others of unexpected changes in the claimed max_fsm_pages need.

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

is a large enough histogram, it will use the number of matches in the
histogram to derive a selectivity estimate, rather than the admittedly
pretty bogus heuristics involving examining the pattern contents.  I set
'large enough' at 100, but perhaps we should change that later.  Also
apply the same technique in contrib/ltree's <@ and @> estimator.  Per
discussion with Stefan Kaltenbrunner and Matteo Beccati.