> >I like the pg_{import,export} names myself ... *nod*
> >
> 
> Sounds fine also; but we have compatibility issues in that we 
> still need pg_dump. Maybe just a symbolic link to pg_export.

Yes, we still need in pg_dump, because of pg_dump is thing
quite different from WAL based backup/restore. pg_dump
is utility to export data in system independant format
using standard SQL commands (with COPY extension) and WAL
based backup system is to export *physical* data files
(and logs). So, pg_dump should be preserved asis.

Vadim

Mon, 16 Oct 2000 15:07:38 -0700
"Mikheev, Vadim" <vmikheev@SECTORBASE.COM>
RE: AW: Backup, restore & pg_dump
At 15:07 16/10/00 -0700, Mikheev, Vadim wrote:
>
>So, pg_dump should be preserved asis.
>

Just to clarify; I have no intention of doing anything nasty to pg_dump.
All I plan to do is rename the pg_restore to one of
pg_load/pg_import/pg_undump/pmud_gp, to make way for a WAL based restore
utility, although as Bruce suggests, this may be premature.



----------------------------------------------------------------
Philip Warner                    |     __---_____
Albatross Consulting Pty. Ltd.   |----/       -  \
(A.B.N. 75 008 659 498)          |          /(@)   ______---_
Tel: (+61) 0500 83 82 81         |                 _________  \
Fax: (+61) 0500 83 82 82         |                 ___________ |
Http://www.rhyme.com.au          |                /           \|
                                 |    --________--
PGP key available upon request,  |  /
and from pgp5.ai.mit.edu:11371   |/

Tue, 17 Oct 2000 11:59:08 +1000
Philip Warner <pjw@rhyme.com.au>
RE: AW: Backup, restore & pg_dump