so no one noticed.

This was not especially critical before, but it is now that we track
ownership dependencies --- the dependency for the rowtype *must* shift
to the new owner.  Spotted by Bernd Helmle.
Also fix a problem introduced by recent change to allow non-superusers
to do ALTER OWNER in some cases: if the table had a toast table, ALTER
OWNER failed *even for superusers*, because the test being applied would
conclude that the new would-be owner had no create rights on pg_toast.
A side-effect of the fix is to disallow changing the ownership of indexes
or toast tables separately from their parent table, which seems a good
idea on the whole.

Done:

< * Prevent inherited tables from expanding temporary subtables of other
> * -Prevent inherited tables from expanding temporary subtables of other

doesn't block the bgwriter from making progress writing out other buffers.
This was a hard problem in the context of the ARC/2Q design, but it's
trivial in the context of clock sweep ... just advance the sweep counter
before we try to write not after.

an inheritance tree.  Per recent discussions.

of special case for Windows port.  Put a PG_TRY around most of createdb()
to ensure that we remove copied subdirectories on failure, even if the
failure happens while creating the pg_database row.  (I think this explains
Oliver Siegmar's recent report.)  Having done that, there's no need for
the fragile assumption that copydir() mustn't ereport(ERROR), so simplify
its API.  Eliminate the old code that used system("cp ...") to copy
subdirectories, in favor of using copydir() on all platforms.  This not
only should allow much better error reporting, but allows us to fsync
the created files before trusting that the copy has succeeded.

may not be obsolete, but since every other readdir loop in our code
has it, I think this should too.

Original patch by Hans-Juergen Schoenig, revisions by Karel Zak
and Tom Lane.

editorialization.

> * -Allow limits on per-db/role connections

< 	o Allow objects to be moved to different schemas
> 	o -Allow objects to be moved to different schemas

Fix word wrap:

< 	* Allow GRANT/REVOKE permissions to be applied to all schema objects with one
< 	  command
> 	o Allow GRANT/REVOKE permissions to be applied to all schema objects
> 	  with one command

object kinds (tables, functions, types).  Documentation is not here yet.
Original code by Bernd Helmle, extensive rework by Bruce Momjian and
Tom Lane.

< 	  This would require a new global table that is dumped to flat file for
< 	  use by the postmaster.  We do a similar thing for pg_shadow currently.
> 	  This would add a function to load the SQL table from
>           pg_hba.conf, and one to writes its contents to the flat file.
> 	  The table should have a line number that is a float so rows
> 	  can be inserted between existing rows, e.g. row 2.5 goes
> 	  between row 2 and row 3.

This patch also includes preliminary update of pg_dumpall for roles.
Petr Jelinek, with review by Bruce Momjian and Tom Lane.

< 	o Allow postgresql.conf file values to be changed via an SQL API
> 	o Allow postgresql.conf file values to be changed via an SQL
> 	  API, perhaps using SET GLOBAL

< 	* Allow server logs to be remotely read using SQL commands
151a151
> * Allow server logs to be remotely read and removed using SQL commands

place.

Alvaro Herrera

count.

Oliver Jowett

tests for the new interval->day changes. I added tests for
justify_hours() and justify_days() to interval.sql, as they take
interval input and produce interval output. If there's a more
appropriate place for them, please let me know.

Michael Glaesemann

<
> * Allow EXPLAIN to identify tables that were skipped because of
>   enable_constraint_exclusion
> * Allow EXPLAIN output to be more easily processed by scripts
760a763
> * Allow enable_constraint_exclusion to work for UPDATE and DELETE queries

<
> * Allow enable_constraint_exclusion to work for UNIONs like it does for
>   inheritance

> * Prevent inherited tables from expanding temporary subtables of other
>   sessions

Chris Browne

> * Add system view to show free space map contents
884c885
< 	o Move into the backend code
> 	o -Move into the backend code

> * Allow SELECT ... FOR UPDATE on inherited tables

< * Add TRUNCATE permission
> * Add a separate TRUNCATE permission

> * Add TRUNCATE permission
>
>   Currently only the owner can TRUNCATE a table because triggers are not
>   called, and the table is locked in exclusive mode.
>