| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Rafael Martinez <r(dot)m(dot)guerrero(at)usit(dot)uio(dot)no> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, rafael(at)postgresql(dot)org(dot)es |
| Subject: | Re: pg_dump and pg_dumpall in real life |
| Date: | 2013-11-11 14:28:51 |
| Message-ID: | 5280E9A3.4010304@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 11/11/2013 08:59 AM, Rafael Martinez wrote:
>
> * It would be great to be able to tell pg_restore that user1 in the
> dump will became user2 in the restored/cloned database. The same for
> the name of the database.
A general ability to rename things would be good. In particular,
restoring schema x into schema y or table x into table y would be very
useful, especially if you need to be able to compare old with new.
Unfortunately, this would involve a fairly significant change in the
design of pg_dump / pg_restore. The stored SQL is currently fairly
opaque, and a renaming scheme would probably need to implement instead
some sort of placeholder mechanism. That would mean a LOT of work.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2013-11-11 14:28:54 | Re: Datatyp of a column |
| Previous Message | Stephen Frost | 2013-11-11 14:24:34 | Re: pg_dump and pg_dumpall in real life |