
> > > As a result do people have any objection to changing pg_restore to
> > > pg_undump? Or pg_load?

Also possible would be a name like Oracle
pg_exp and pg_imp for export and import.
(or pg_export and pg_import)

Load and unload is often more tied to data only (no dml).

I agree that the current name pg_restore for its current functionality
is not good and misleading in the light of WAL backup. 

Andreas

Mon, 16 Oct 2000 12:23:56 +0200
Zeugswetter Andreas SB <ZeugswetterA@wien.spardat.at>
AW: Backup, restore & pg_dump

I like the pg_{import,export} names myself ... *nod*


On Mon, 16 Oct 2000, Zeugswetter Andreas SB wrote:

> 
> > > > As a result do people have any objection to changing pg_restore to
> > > > pg_undump? Or pg_load?
> 
> Also possible would be a name like Oracle
> pg_exp and pg_imp for export and import.
> (or pg_export and pg_import)
> 
> Load and unload is often more tied to data only (no dml).
> 
> I agree that the current name pg_restore for its current functionality
> is not good and misleading in the light of WAL backup. 
> 
> Andreas
> 
> 

Marc G. Fournier                   ICQ#7615664               IRC Nick: Scrappy
Systems Administrator @ hub.org 
primary: scrappy@hub.org           secondary: scrappy@{freebsd|postgresql}.org 


Mon, 16 Oct 2000 10:08:50 -0300 (ADT)
The Hermit Hacker <scrappy@hub.org>
Re: AW: Backup, restore & pg_dump
Philip Warner writes:

> >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.

I'm not so fond of changing a long-established program name for the sake
of ethymological correctness or consistency with other products (yeah,
right).  I got plenty of suggestions if you want to start that.  I say
stick to pg_dump[all], and name the inverse pg_undump, pg_load, or
pmud_gp.

Btw., it will still be possible to restore, er, reload, with psql, right?

-- 
Peter Eisentraut      peter_e@gmx.net       http://yi.org/peter-e/


Tue, 17 Oct 2000 00:12:59 +0200 (CEST)
Peter Eisentraut <peter_e@gmx.net>
Re: AW: Backup, restore & pg_dump
> Philip Warner writes:
> 
> > >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.
> 
> I'm not so fond of changing a long-established program name for the sake
> of ethymological correctness or consistency with other products (yeah,

Agreed.



-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

Mon, 16 Oct 2000 18:15:53 -0400 (EDT)
Bruce Momjian <pgman@candle.pha.pa.us>
Re: AW: Backup, restore & pg_dump
At 10:08 16/10/00 -0300, The Hermit Hacker wrote:
>
>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.


----------------------------------------------------------------
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 08:51:11 +1000
Philip Warner <pjw@rhyme.com.au>
Re: AW: Backup, restore & pg_dump
On Tue, 17 Oct 2000, Peter Eisentraut wrote:

> Philip Warner writes:
> 
> > >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.
> 
> I'm not so fond of changing a long-established program name for the sake
> of ethymological correctness or consistency with other products (yeah,
> right).  I got plenty of suggestions if you want to start that.  I say
> stick to pg_dump[all], and name the inverse pg_undump, pg_load, or
> pmud_gp.

pmud_gp? *raised eyebrow*



Mon, 16 Oct 2000 19:51:48 -0300 (ADT)
The Hermit Hacker <scrappy@hub.org>
Re: AW: Backup, restore & pg_dump
At 00:12 17/10/00 +0200, Peter Eisentraut wrote:
>
>Btw., it will still be possible to restore, er, reload, with psql, right?
>

Correct.


----------------------------------------------------------------
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:56:04 +1000
Philip Warner <pjw@rhyme.com.au>
Re: AW: Backup, restore & pg_dump