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 [EMAIL PROTECTED] http://yi.org/peter-e/
- AW: [HACKERS] Backup, restore & pg_dump Zeugswetter Andreas SB
- Re: AW: [HACKERS] Backup, restore & pg_dum... The Hermit Hacker
- Re: AW: [HACKERS] Backup, restore & pg... Philip Warner
- Re: AW: [HACKERS] Backup, restore &... Peter Eisentraut
- Re: AW: [HACKERS] Backup, restore ... Bruce Momjian
- Re: AW: [HACKERS] Backup, restore ... The Hermit Hacker
- Re: AW: [HACKERS] Backup, restore ... Philip Warner
- RE: AW: [HACKERS] Backup, restore & pg_dum... Mikheev, Vadim
- RE: AW: [HACKERS] Backup, restore & pg... Philip Warner
- Re: AW: [HACKERS] Backup, restore & pg_dum... Mikheev, Vadim
- RE: AW: [HACKERS] Backup, restore & pg_dum... Mikheev, Vadim
- RE: AW: [HACKERS] Backup, restore & pg_dum... Mikheev, Vadim
