Re: AW: Backup, restore & pg_dump - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: AW: Backup, restore & pg_dump
Date
Msg-id Pine.LNX.4.21.0010170007560.862-100000@peter.localdomain
Whole thread Raw
In response to Re: AW: Backup, restore & pg_dump  (Philip Warner <pjw@rhyme.com.au>)
Responses Re: AW: Backup, restore & pg_dump
Re: AW: Backup, restore & pg_dump
Re: AW: Backup, restore & pg_dump
List pgsql-hackers
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/



pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: AW: new relkind for view
Next
From: Bruce Momjian
Date:
Subject: Re: AW: Backup, restore & pg_dump