Per Yoshinori Ariie's report.

> * Have pg_dump use ADD PRIMARY KEY after COPY, for performance (Neil Conway)

1) Handle parameter array.
2) Allow re-use of the connection handle after SQLDisconnect.
3) Reject NULL if no indicator specified.
4) Improve the handling of '_' in table name.
5) Unify internal begin/commit/abort operations.
6) Change SQLTables() to return null not "" for the
   table_owner.
7) Fix a bug about parameter handling reported by Benoit Menendez.
8) Add cast in handling ODBC date/time escape sequences.
9) Fix a bug about cache_size handing in declare/fetch mode.

[ODBC3.0 related]
10) Improve the handling of descriptor handles(ODBC3.0).
11) Improve the type handling of some types for ODBC3.0.

[Thanks to Marcelo Aceto for his useful patches]
12) Allow nested ODBC escape.
13) Allow changing autocommit on/off inside the transaction
    block.
14) Improve the handling of ODBC scalar functions.

> * Have pg_dump use ADD PRIMARY KEY after COPY, for performance

> * ODBC
> 	o ODBC 3.0 support
> 	o Unicode(UCS-2) support
> 	o Updatable cursors support

primary keys after the fact!

Also, we need to add regression tests for alter table / add primary key
and alter table / drop constraint.  These shouldn't be added until 7.3
tho
methinks...

Chris

e.g. table contraint definition -> table_constraint_definition.

originally created with, so that the set of visible tuples does not
change as a result of other activity.  This essentially makes PG cursors
INSENSITIVE per the SQL92 definition.  See bug report of 13-Feb-02.

was mentioned on the man page for the underlying CREATE USER command,
but it should be explained here too.

This restores the Linux behavior to what it was in PG 7.0 and 7.1, and
causes other platforms to agree.  (Other well-tested platforms like HPUX
were doing it this way already.)  Per pghackers discussion over the past
month or so.

(backslash-r, backslash-n) for protection against newline-conversion
munging.  In future we will also tweak COPY FROM, but this part of the
change should be backwards-compatible.  Per pghackers discussion.
Also, update COPY reference page to describe the backslash conversions
more completely and accurately.

of pointers is required.  Patch from Teodor Sigaev per pghackers
discussion.  It's an ugly kluge but avoids forcing initdb; we'll put
a better fix into 7.3 or later.

inner indexscan (ie, one with runtime keys).  ExecIndexReScan must
compute or recompute runtime keys even if we are rescanning in the
EPQ case.  TidScan seems to have comparable problems.  Per bug
noted by Barry Lind 11-Feb-02.

< 	o prevent lose of indexes, permissions, inheritance (Bruce)
---
> 	o prevent loss of indexes, permissions, inheritance (Bruce)

the CREATE DATABASE command right in pg_dump -C case.

into a virgin database, ie, one created from template0, if there are any
site-local additions in template1.

crash on Solaris when over disk quota.  Instead, report such failures
via elog(DEBUG).

< * Have checkpoint process identify itself via ps status display

> * Have checkpoint process identify itself via ps status display

Patch from sugita@sra.co.jp.

Teodor Sigaev <teodor@stack.net>.