UNIQUE and DISTINCT predicates are both listed as implemented -- AFAIK,
neither is.

I also included another trivial patch which adds the default location
of the DSSSL stylesheets on my system (Debian unstable, docbook-dsssl
1.76) to the list of paths that configure looks for.

Neil Conway

< * Use our own getopt() for FreeBSD/OpenBSD to allow --xxx flags (Bruce)

warnings, and we now look for getopt_long in libgetopt.a.

configure.in.

so that dependencies in default expressions (on operators, functions,
etc) can be expressed properly.

this thing.

Fix comment.c to not depend on parser token values, per discussion awhile
back.

scans that will most likely be caused by SearchSysCache probes.  Also,
share some code between index deletion and table deletion.

varno of index's relation is not 1.  This embarrassing oversight pointed
out by Dmitry Tkach 12-Jul-02.

> o -Add ALTER TABLE DROP non-CHECK CONSTRAINT
> * -Allow psql \d to show foreign keys
> * -Auto-destroy sequence on DROP of table with SERIAL; perhaps a separate
> * -Prevent column dropping if column is used by foreign key
> * -Automatically drop constraints/functions when object is dropped
> * -Make foreign key constraints clearer in dump file
> * -Make foreign keys easier to identify

o -Add SET or BEGIN timeout parameter to cancel query
> * -Add pg_depend table for dependency recording; use sysrelid, oid,

zero turns off the timer.

pg_relcheck is gone; CHECK, UNIQUE, PRIMARY KEY, and FOREIGN KEY
constraints all have real live entries in pg_constraint.  pg_depend
exists, and RESTRICT/CASCADE options work on most kinds of DROP;
however, pg_depend is not yet very well populated with dependencies.
(Most of the ones that are present at this point just replace formerly
hardwired associations, such as the implicit drop of a relation's pg_type
entry when the relation is dropped.)  Need to add more logic to create
dependency entries, improve pg_dump to dump constraints in place of
indexes and triggers, and add some regression tests.

It used to return them as a,b in one row, and now returns
a in one row, and b in one row

2) Change default build mode to multibyte(Windows).

< * Add version file format stamp to heap and other table types

< * Use BlockNumber rather than int where appropriate

as discussed on hackers.

This is the first cut toward CREATE CONVERSION/DROP CONVERSION implementaion.
The commands can now add/remove tuples to the new pg_conversion system
catalog, but that's all. Still need work to make them actually working.
Documentations, regression tests also need work.

> * -Add ALTER TRIGGER ... RENAME

	int32           domainTypMod = NULL;

should be:

	int32           domainTypMod = 0;

> * -Make one version of simple_prompt() in code (Bruce, Tom)