The attached patch allows views to have default values. You can't
specify a default value within a CREATE VIEW statement, it must be
done using ALTER TABLE ... ALTER COLUMN ... SET DEFAULT after the
view has already been created. Most of the hard work was done by
Tom Lane, I just patched pg_dump and updated the documentation.

Neil Conway <neilconway@rogers.com>

Please note I have no way to test this.  Docbook doesn't like my
cygwin setup.

--
Rod Taylor

> * Improve ability to display optimizer analysis using OPTIMIZER_DEBUG

> * -Use faster flex flags for performance improvement (Peter E)

> * -Allow user to control trigger firing order (Tom)
> * -Compile in syslog functionaility by default (Tatsuo)

> * -Allow user to control trigger firing order
> * Add ALTER TRIGGER ... RENAME

 capabilities of specifying time zones as intervals per SQL9x.
Put refentrytitle contents on the same line as the tag.
 Otherwise, leading whitespace is propagated into the product, which
 (at least) messes up the ToC layout.
Remove (some) docinfo tags containing dates. Best to omit if the dates
 are not accurate; maybe use CVS dates instead or leave them out.

different privilege bits (might as well make use of the space we were
wasting on padding).  EXECUTE and USAGE bits for procedures, languages
now are separate privileges instead of being overlaid on SELECT.  Add
privileges for namespaces and databases.  The GRANT and REVOKE commands
work for these object types, but we don't actually enforce the privileges
yet...

_RETURN now, since there's no need to keep 'em unique anymore.

(tgrelid, tgname).  This provides an additional check on trigger name
uniqueness per-table (which was already enforced by the code anyway).
With this change, RelationBuildTriggers will read the triggers in
order by tgname, since it's scanning using this index.  Since a
predictable trigger ordering has been requested for some time, document
this behavior as a feature.  Also document that rules fire in name
order, since yesterday's changes to pg_rewrite indexing cause that too.

DROP RULE and COMMENT ON RULE syntax adds an 'ON tablename' clause,
similar to TRIGGER syntaxes.  To allow loading of existing pg_dump
files containing COMMENT ON RULE, the COMMENT code will still accept
the old syntax --- but only if the target rulename is unique across
the whole database.

< 	  without using PL/PgSQL EXECUTE, needs cached plan invalidation
> 	  without using PL/PgSQL EXECUTE, needs cache prevention/invalidation

> 	o Abort all, some or, no SET changes made in an aborted transaction

> 	o Abort all or commit all SET changes made in an aborted transaction

> 	o Allow Java server-side programming, http://pljava.sourceforge.net
> 	  [java]

> * Rod is Rod Taylor <rbt@zort.ca>

> * Cache most recent query plan(s) (Neil) [prepare]
> * Neil is Neil Conway <nconway@klamath.dyndns.org>

>   using a sequential scan for highest/lowest values (Oleg)

Add to DROP COLUMN description.

> 	o Abort SET changes made in aborted transactions (?)

> * Add BETWEEN ASYMMETRIC/SYMMETRIC (Christopher)
> * Christopher is Christopher Kings-Lynne <chriskl@familyhealth.com.au>

> * Add BSD-licensed qsort() for Solaris

> 	o Allow SHOW to output as a query result, like EXPLAIN

> * Try flex flags -Cf and -CF to see if performance improves

> * Add utility to compute accurate random_page_cost value

an 'opclass owner' column in pg_opclass.  Nothing is done with it at
present, but since there are plans to invent a CREATE OPERATOR CLASS
command soon, we'll probably want DROP OPERATOR CLASS too, which
suggests that a notion of ownership would be a good idea.

> * Allow easy display of usernames in a group