< * -Have sequence dependency track use of DEFAULT sequences

< * Have sequence dependency track use of DEFAULT sequences,
<   seqname.nextval?
> * -Have sequence dependency track use of DEFAULT sequences

was created on a machine with alignment rules and floating-point format
similar to the current machine.  Per recent discussion, this seems like
a good idea with the increasing prevalence of 32/64 bit environments.

argument as a 'regclass' value instead of a text string.  The frontend
conversion of text string to pg_class OID is now encapsulated as an
implicitly-invocable coercion from text to regclass.  This provides
backwards compatibility to the old behavior when the sequence argument
is explicitly typed as 'text'.  When the argument is just an unadorned
literal string, it will be taken as 'regclass', which means that the
stored representation will be an OID.  This solves longstanding problems
with renaming sequences that are referenced in default expressions, as
well as new-in-8.1 problems with renaming such sequences' schemas or
moving them to another schema.  All per recent discussion.
Along the way, fix some rather serious problems in dbmirror's support
for mirroring sequence operations (int4 vs int8 confusion for instance).

the ProcessUtility case, resulting in an intratransaction memory leak
if a utility command actually did return any tuples, as reported by
Dmitry Karasik.  Fix this and also make the behavior more consistent
for cases involving nested SPI operations and multiple query trees,
by ensuring that we store the state locally until it is ready to be
returned to the caller.

a few typos in comments.

The dictionaries I checked list "altho" as a variant of "although,"
but I didn't find any other instances of the former in the source
tree so I changed it.

Michael Fuhr

SQL option spelling.

Also, make pg_total_relation_size include the size of the
TOAST index.

Patches Contributed by Tomoaki Sato.

only the inner-side relation would be considered as potential equijoin clauses,
which is wrong because the condition doesn't necessarily hold above the point
of the outer join.  Per test case from Kevin Grittner (bug#1916).

subsystem reliability.

Victor Vislobokov

< * +Add options to pg_config to show the share_dir, sysconfdir,
<   pkgincludedir, and localedir

building contrib with USE_PGXS.  To make it work all the way, the
pg_regress script would need to be included in the installation tree.

relocated after installation.  We can't trust the installation paths
inserted into Makefile.global by configure, so instead we must get the
paths from pg_config.  This requires extending pg_config to support all
the separately-configurable path names, but that was on TODO anyway.

to avoid useless multiple executions of pg_config.

to be less error-prone.

> 	o Improve signal handling,
> 	  http://archives.postgresql.org/pgsql-patches/2005-06/msg00027.php

< * Add options to pg_config to show the share_dir, sysconfdir,
> * +Add options to pg_config to show the share_dir, sysconfdir,

out-of-memory --- that is, return NULL rather than dumping core.
Noted by Qingqing Zhou.

Marko Kreen

< * Allow protocol-level EXECUTE that is actually a fetch to appear
<   in the logs as a fetch rather than another execute

adjusted from a patch by Simon.

> * Allow protocol-level BIND parameter values to be logged
> * Allow protocol-level EXECUTE that is actually a fetch to appear
>   in the logs as a fetch rather than another execute