except that it's more robust, reconnects less often, and is NLS'ed.

Use off_t and size_t in pg_dump to handle file offset arithmetic correctly.

The -n and -N options were removed.  Quoting is now smart enough to
supply quotes if and only if necessary.

Numerical types are now printed without quotes, except in cases of
special values such as NaN.

Boolean values printed as true and false.

Most string literals now do not escape whitespace characters (newlines,
etc.) for portability.

SET SESSION AUTHORIZATION argument is a string literal, to follow SQL.

Made commands output by pg_dump use consistent spacing and indentation.

and database.  In particular, make script wrappers understand the
PGDATABASE environment variable.

as it appears in the schema dump, and index tags.

Fix pg_dump to not quote the function name in the storage tag.
Fix pg_dump so GRANT/REVOKE(ACL) tag entries are not quoted, for
	consistency.
Fix pg_restore to properly handle quotes and some spaces in -P.

a spelling mistake and deletes an antiquated comment.

Neil Conway

that would do the wrong thing with BLOB OIDs exceeding 2G.

having names conflicting with system objects will work --- the search
path is now user-schema, pg_catalog rather than implicitly the other way
around.  Note this requires being careful to explicitly qualify references
to system names whenever pg_catalog is not first in the search path.
Also, add support for dumping ACLs of schemas.

but the basic capability seems to work.

in hopes of making erroneous usage more apparent.  Per discussion 15-Apr.

Mario Weilguni

the CREATE DATABASE command right in pg_dump -C case.

tom lane

dumped by pg_dump -o.  Per bug report posted by Bruce; fix is from
Philip Warner, reviewed by Tom Lane.

(surprised no one has reported these yet...)

initdb/regression tests pass.

- Fix handling of {data/schema}-only restores when using a full
  backup file; prior version was restoring schema in data-only
  restores. Added enum to make code easier to understand.

tests pass.

(why bother dropping individual objects in a just-created database?)
as well as dangerous (as the code stands, the drops will be issued in
the wrong database, namely the one you were originally connected to).

in messages and documentation.

\connect, to avoid possible password prompts and such, at the drawback of
having to have superuser access.

Don't hardcode the maximum accepted server version, use PG_VERSION instead.
Install a notice processor so notices are handled like error messages.
Word smithing.

--verbose messages, which had not been considered so far.  Output to the
terminal should okay now; comments written into the dump are still English
only, which may or may not be the desirable thing.

message clean up.

specification of username (like in psql).  pg_dumpall now works with
password authentication.

 - Fix view dumping SQL for V7.0
 - Fix bug when getting view oid with long view names
 - Treat SEQUENCE SET TOC entries as data entries rather than schema
   entries.
 - Make allowance for data entries that did not have a data dumper
   routine (eg. SEQUENCE SET)

- pgsql v7.0 compatbility

- Fix crash due to null string pointer in some tar files with some libs

the UDT/function order problem.

    - Rudimentary support for dependencies in archives.
      Uses dependencies to modify the OID used in sorting TOC
      entries. This will NOT handle multi-level dependencies,
      but will manage simple relationships like UDTs & their functions.

    - Treat OIDs with more respect (avoid using ints, use macros
      for conversion & comparison).

 - Avoid forcing table name to lower case in FixupBlobXrefs
 - Removed fmtId calls for all ArchiveEntry name fields. This fixes
   quoting problems in trigger enable/disable code for mixed case
   table names, and avoids commands like 'pg_restore -t '"TblA"'

which caused segfault in a data-only retore with BLOBs

- Use exact table names when enabling/disabling triggers

- Change -U option to -L to allow -U to specify username in future. (pg_restore)

on some platforms, which is not too surprising considering how platform
specific these macros must be).