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.

Use pg_get_constraintdef instead of pg_constraint.consrc
Use UNION ALL instread of UNION
Make use of regclass type for getting OID of system catalogs
Add schema qualifications where necessary
Fix typos

well spotted by Neil Conway.

never documented anywhere, sigh).  Centralize the detailed documentation
of system views into catalogs.sgml, and provide cross-references.

Link to it from some appropriate places.

digits, and label it 'ms' not 'msec', for consistency with psql's \timing
display.  Per recent discussions.

a portion of a patch recently submitted by Christopher Kings-Lynne.
Applied by agreement that this is a bug fix.

tab-completing.

of the entries used to be zero, which I think I had deliberately done in
the name of saving cycles during ANALYZE, but it was really a rather
foolish decision.  Some of the more complex views in information_schema
were getting really bad plans for lack of statistics on the columns they
were joining over.

I'm not forcing an initdb for this, but I think there will be one soon
anyway to repair some bugs in the information_schema views.

memory say 'out of shared memory'; some were doing that and some just
said 'out of memory'.  Also add a HINT about increasing max_locks_per_transaction
where relevant, per suggestion from Sean Chittenden.  (The former change
does not break the strings freeze; the latter does, but I think it's
worth doing anyway.)

identifiers --- it will now complete these correctly with double quoting.
Fix a few other issues in passing.