< * Consider use of open/fcntl(O_DIRECT) to minimize OS caching
> * Consider use of open/fcntl(O_DIRECT) to minimize OS caching,
>   especially for WAL writes

Windows. Patch from Magnus Hagander.

during flat-file writing.  The only difference is that SnapshotSelf
would consider tuples of the 'current command' within the current
transaction as valid, where SnapshotNow wouldn't.  We can eliminate
the need for this with one extra CommandCounterIncrement call before
we start reading the catalogs.

the AMI_OVERRIDE flag.  The fact that TransactionLogFetch treats
BootstrapTransactionId as always committed is sufficient to make
bootstrap work, and getting rid of extra tests in heavily used code
paths seems like a win.  The files produced by initdb are demonstrably
the same after this change.

deleted tuples. Of course it is only to be used for disaster recovery.

file now identifies group members by usesysid not name; this avoids
needing to depend on SearchSysCache which we can't use during startup.
(The old representation was entirely broken anyway, since we did not
regenerate the file following RENAME USER.)  It's only a 95% solution
because if the group membership list is big enough to be toasted out
of line, we cannot read it during startup.  I think this will do for
the moment, until we have time to implement the planned pg_role
replacement for pg_group.

in GetNewTransactionId().  Since the limit value has to be computed
before we run any real transactions, this requires adding code to database
startup to scan pg_database and determine the oldest datfrozenxid.
This can conveniently be combined with the first stage of an attack on
the problem that the 'flat file' copies of pg_shadow and pg_group are
not properly updated during WAL recovery.  The code I've added to
startup resides in a new file src/backend/utils/init/flatfiles.c, and
it is responsible for rewriting the flat files as well as initializing
the XID wraparound limit value.  This will eventually allow us to get
rid of GetRawDatabaseInfo too, but we'll need an initdb so we can add
a trigger to pg_database.

CHECKPOINT and some other commands in the context of a standalone
backend.  Allow a standalone backend to do its own checkpoints.

into the sub-SELECT targetlist when it appears in the context
INSERT INTO foo SELECT $1 ...  Per report from Abhijit Menon-Sen.

    <H4><A name="4.20">4.20</A>) Why do I get "missing oid" errors when
    accessing temporary tables in PL/PgSQL functions?</H4>

Merlin Moncure

<   The agreed syntax is:
>   The proposed syntax is:

>   The agreed syntax is:
> 	GRANT SELECT ON ALL TABLES IN public TO phpuser;
> 	GRANT SELECT ON NEW TABLES IN public TO phpuser;
>

Manfred Koizar

< 	o Allow COPY FROM ... CVS to interpret newlines and carriage
> 	o Allow COPY FROM ... CSV to interpret newlines and carriage

> * Add xpath_array() to /contrib/xml2 to return results as an array

non-HAVE_SIGPROCMASK cases in pqinitmask().

non-HAVE_SIGPROCMASK cases in pqinitmask().

> * Allow the creation of indexes with mixed ascending/descending specifiers

> * Make src/port/snprintf.c thread-safe

Backpatch to 8.0.X.

DEBUG.

< * Add IP address to pg_stat_activity
> * Add the client IP address to pg_stat_activity

> * Add IP address to pg_stat_activity

DEBUG.

Fix a few places where DEBUG1 crept in that should have been DEBUG2.

works (and max_stack_depth is not set too high for the platform).
Inspired by trouble report from Brian Betts.

	SELECT CURRENT_TIMESTAMP;
	SELECT now();
	SELECT TIMESTAMP 'now';  -- incorrect for use with DEFAULT