Dave Page

 Jun Kuwamura

renamed to --log-file for clarity.

Make pgbench "script driven" to eliminate hard coded transaction
scenario. (Tatsuo Ishii)

Somehow I missed some parser changes, so this commit comes pretty late. I just synced the parser of ecpg against the backend version, but still have to sync the lexer.

Also I fixed a bug in a bug fix I committed a few weeks ago. he check for a varchar pointer was incomplete.

Per buildfarm results and Michael Fuhr.

where it should prohibit COPY FROM.  Found by Alon Goldshuv.

sort operations.  Per recent discussion.  Simon Riggs and Tom Lane.

for using it for other things besides VACUUM.

Update release dates for pending back-branch releases.

early binding for nextval() calls in default clauses.

< * -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).