| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Philip Warner <pjw(at)rhyme(dot)com(dot)au> |
| Cc: | The Hermit Hacker <scrappy(at)hub(dot)org>, Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: AW: Backup, restore & pg_dump |
| Date: | 2000-10-16 22:12:59 |
| Message-ID: | Pine.LNX.4.21.0010170007560.862-100000@peter.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)gmx(dot)net http://yi.org/peter-e/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2000-10-16 22:15:53 | Re: AW: Backup, restore & pg_dump |
| Previous Message | Mikheev, Vadim | 2000-10-16 22:07:38 | RE: AW: Backup, restore & pg_dump |