output column are not emitted.  (That change already caused more noise in
the regression test output files than I would like.)  Provide some needed
editorial help for comments, clean up code formatting.

        o Allow an existing index to be marked as a table's primary key
>
> 	  http://archives.postgresql.org/pgsql-hackers/2008-04/msg00500.php

> 	o Allow an existing index to be marked as a table's primary key

* Add column to pg_stat_activity that shows the progress of long-running
  commands like CREATE INDEX and VACUUM
>
>   http://archives.postgresql.org/pgsql-patches/2008-04/msg00203.php
>

> 	o Clear table counters on TRUNCATE
>
> 	  http://archives.postgresql.org/pgsql-hackers/2008-04/msg00169.php

> 	o -Prevent parent tables from altering or dropping constraints
> 	o -Prevent child tables from altering or dropping constraints

as those for inherited columns; that is, it's no longer allowed for a child
table to not have a check constraint matching one that exists on a parent.
This satisfies the principle of least surprise (rows selected from the parent
will always appear to meet its check constraints) and eliminates some
longstanding bogosity in pg_dump, which formerly had to guess about whether
check constraints were really inherited or not.

The implementation involves adding conislocal and coninhcount columns to
pg_constraint (paralleling attislocal and attinhcount in pg_attribute)
and refactoring various ALTER TABLE actions to be more like those for
columns.

Alex Hunsaker, Nikhil Sontakke, Tom Lane

Improve logic for finding object files on OBJS lines in contrib Makefiles. If this unbreaks buildfarm mastodon, apply everywhere.

Also, clean up the code that assigned the scale into :scale variables.
Greg Smith and Tom Lane

began to realize that the input() function isn't used and printed warnings.

parameter. This fixes bug 4137 reported by Wojciech Strzalka, where a WAL
file is deleted too early when starting the recovery of a warm standby server.

Also add a sanity check in pg_standby so that it will refuse to delete anything
earlier than the file being restored, and improve the debug message in case
nothing is deleted.

Simon Riggs. Backpatch to 8.3, which is where %r was introduced.

something was wrong with that tab patch.

pg_wcsformat without changing pg_wcssize to match.  Add some comments to
try to make that clearer, and make a couple other minor editorializations.

>
> * Improve the /contrib installation experience
>
>   http://archives.postgresql.org/pgsql-hackers/2008-04/msg00132.php

adjust source code to be more modular.

return 1, rather than error.

This was already the float8 behavior.

file/pipe output too if \pset columns' is set.

Bryce Nesbitt

auto-configure properly for libxslt present or not.

specify the column names and types. Also simplifies the view.

Per comments from Tom.

< * Improve detection of shared memory segments being used by other
<   FreeBSD jails

> * Improve detection of shared memory segments being used by others
>   by checking the SysV shared memory field 'nattch'
>   http://archives.postgresql.org/pgsql-hackers/2008-01/msg00673.php

>
> 	o Add CREATE SCHEMA ... LIKE that copies a schema
>

> * Add database and transaction-level triggers
>
>   http://archives.postgresql.org/pgsql-hackers/2008-03/msg00451.php

Scott Marlowe

instead of calling a bunch of individual functions.

This function can also be called directly, taking a PID as an argument, to
return only the data for a single PID.

< * Consider increasing the number of default statistics target, and
<   reduce statistics target overhead

< 	o Allow dictionary to filter out only stop words
> 	o Allow dictionaries to change the token that is passed on to
> 	  later dictionaries

        o Consider changing error to warning for strings larger than one
          megabyte

          http://archives.postgresql.org/pgsql-bugs/2008-02/msg00190.php
          http://archives.postgresql.org/pgsql-patches/2008-03/msg00062.php

than only 'off'.

Not clear that there's any observable bug at present from this omission,
but it seems like something to fix going forward.

to avoid the pain of manually renumbering them anytime we insert another
name in alphabetical order.  An excellent idea from Alex Hunsaker and
NikhilS' inherited-constraints patch --- whether or not the rest of that
gets in, this should.  Dunno why we never thought of it before.

file:

	http://www.postgresql.org/download