> 	o Have COPY return number of rows loaded/unloaded

> * Add checks for fclose() failure

extensions to support our historical behavior.  An aggregate belongs
to the closest query level of any of the variables in its argument,
or the current query level if there are no variables (e.g., COUNT(*)).
The implementation involves adding an agglevelsup field to Aggref,
and treating outer aggregates like outer variables at planning time.

> * Allow logging of only data definition(DDL), or DDL and modification statements

> * Allow a single index to index multiple tables (for inheritance and subtables)
408a410
> * Improve the planner to use CHECK constraints to prune the plan (for subtables)
418a421
> * Allow partitioning of table into multiple subtables
419a423
> T

> * Allow SET CONSTRAINTS to be qualified by schema/table

> * Add config variable to prevent auto-adding missing FROM-clause tables

> * Prevent whole-row references from leaking memory, e.g. SELECT COUNT(tab.*)

> * Consider using MVCC to cache count(*) queries with no WHERE clause

for grammar-detected problems.  Revert Makefile hack that kept it looking
like the pre-bison-1.875 output.

of an index can now be a computed expression instead of a simple variable.
Restrictions on expressions are the same as for predicates (only immutable
functions, no sub-selects).  This fixes problems recently introduced with
inlining SQL functions, because the inlining transformation is applied to
both expression trees so the planner can still match them up.  Along the
way, improve efficiency of handling index predicates (both predicates and
index expressions are now cached by the relcache) and fix 7.3 oversight
that didn't record dependencies of predicate expressions.

docs that CLIENT/LOG_MIN_MESSAGES now controls debug_* output location.
Doc changes included.

< * Add now("transaction|statement|clock") functionality
> * Add transaction_timestamp(), statement_timestamp(), clock_timestamp() functionality

modify passwords, per user confusion report.

Also clean up wording that command line utils need database access.

> * Allow UPDATE to use SET col = DEFAULT

blanks, in hopes of reducing the surprise factor for newbies.  Remove
redundant operators for VARCHAR (it depends wholly on TEXT operations now).
Clean up resolution of ambiguous operators/functions to avoid surprising
choices for domains: domains are treated as equivalent to their base types
and binary-coercibility is no longer considered a preference item when
choosing among multiple operators/functions.  IsBinaryCoercible now correctly
reflects the notion that you need *only* relabel the type to get from type
A to type B: that is, a domain is binary-coercible to its base type, but
not vice versa.  Various marginal cleanup, including merging the essentially
duplicate resolution code in parse_func.c and parse_oper.c.  Improve opr_sanity
regression test to understand about binary compatibility (using pg_cast),
and fix a couple of small errors in the catalogs revealed thereby.
Restructure "special operator" handling to fetch operators via index opclasses
rather than hardwiring assumptions about names (cleans up the pattern_ops
stuff a little).

< * Update clients to use data types, typmod, schema.table.column names of
<   result sets using new query protocol
453a452,453
> 	o Update clients to use data types, typmod, schema.table.column names of
> 	  result sets using new query protocol

< * Allow clients to get data types, typmod, schema.table.column names from
<   result sets, either via the backend protocol or a new QUERYINFO command

to:

> * Update clients to use data types, typmod, schema.table.column names of
>   result sets using new query protocol

> * Allow clients to get data types, typmod, schema.table.column names from
>   result sets, either via the backend protocol or a new QUERYINFO command