< 	o Queries across databases or servers (two-phase commit) [2phase]
> 	o Queries across databases or servers (two-phase commit)

> 	o Queries across databases or servers (two-phase commit) [2phase]

gcc.  Per comment from original author, Brian Gallew:
"Ancient history.  Kill it fast."

language handler to the 'Internals' area, per my proposal of yesterday.
Clean up the trigger documentation a bit.  Push SPI chapter to the end
of its part, and reorder the Internals chapters into what seems a more
sensible order (at the moment anyway).

> * Allow functions to have a search path specified at creation time

Avoids warnings from newer bisons.

up configure to beta5

better way to keep these in sync...

and add binary send/receive functions.  Fix some other grottiness such
as failure to mark the C functions STRICT.

of the book.  Fix it.

are properly schema-qualified.

Christopher Kings-Lynne

< 	o Allow BINARY option to SELECT, just like DECLARE

< * Allow INET subnet tests to use indexes
> * Allow INET subnet tests using non-constants to be indexed

LLONG_MIN.  One example is AIX, per report from Andreas.

on Windows; per complaint from Andreas that it breaks AIX build.

against a 7.0 server.

Christopher Kings-Lynne

< * Allow INET subnet tests using non-constants
> * Allow INET subnet tests to use indexes
101a102
> 	o Allow MIN()/MAX() on arrays
144c145
< * Allow CREATE INDEX zman_index ON test (date_trunc( 'day', zman ) datetime_ops)
> * -Allow CREATE INDEX zman_index ON test (date_trunc( 'day', zman ) datetime_ops)
166c167
< * Improve handling of index scans for NULL
> * Allow use of indexes to search for NULLs
203a205
> * Add optional textual message to NOTIFY
252c254
< 	o Add SET SCHEMA
> 	o Add SET PATH for schemas
297a300
> * Allow fastpast to pass values in portable format
344a348
> * Allow statement-level triggers to access modified rows
526d529
< 	o Add optional textual message to NOTIFY
530d532
< 	o Allow fastpast to pass values in portable format
533c535
< 	o Special passing of binary values in platform-neutral format (bytea?)
> 	o -Special passing of binary values in platform-neutral format (bytea?)

     <listitem><para> Dollar sign (<literal>$</>) is no longer allowed
	in operator names</para></listitem>
     <listitem><para> Dollar sign (<literal>$</>) can be a non-first
	character in identifiers</para></listitem>

the user is confused about whether -f is input or output file.

subquery that didn't previously have one.  We have traditionally made
the caller of ResolveNew responsible for updating the hasSubLinks flag
of the outermost query, but this fails to account for hasSubLinks in
subqueries.  Fix ResolveNew to handle this.  We might later want to
change the calling convention of ResolveNew so that it can fix the
outer query too, simplifying callers.  But I went with the localized
fix for now.  Per bug report from J Smith, 20-Oct-03.

behavior reported by Martin Marques.

to ensure any needed compiler support routines are included.  This is
arguably appropriate on *every* gcc platform, but for the moment I'll take
the conservative approach of only doing it on a platform where it's
provably useful.  Per complaint from Heiko Lehmann, 13-Feb-03, as well
as personal experience --- contrib/pgstattuple has never worked for me,
but it does now.

test was updated previously, but documentation is lagging.

data, and both have filled the transmission buffers.  One scenario where
this can happen was illustrated here:
http://archives.postgresql.org/pgsql-hackers/2003-04/msg00979.php

machine readable, without headers, not sorted.  Parameter descriptions
adjusted to fit first sentence + rest convention.

fully search-path-proof yet; also, element_types view did not work for
parameters and result types of functions, because it didn't generate
the object_name for the function the same way the data_type_privileges
view does.  While at it, centralize dependencies on INDEX_MAX_KEYS/
FUNC_MAX_ARGS into a function returning setof int, so that it will be
easier to fix information_schema for nonstandard values of these
parameters.

I inadvertently broke a few days ago (per report from Sean Thomas).
Add regression test case to try to catch any similar breakage in future.