From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
---|---|
To: | Naz Gassiep <naz(at)mira(dot)net> |
Cc: | Andreas Joseph Krogh <andreak(at)officenet(dot)no>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: pg_dump schema breakup |
Date: | 2006-08-18 17:39:38 |
Message-ID: | 44E5FB5A.6000901@commandprompt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
>>> I think what you may really be after is "the stuff that should be loaded
>>> before inserting data" and "the stuff that should be loaded after", but
>>> the above are poor names for these concepts.
>>>
>>
>> But it certainly would be nice to be able to dump all that "stuff":-)
> Yea, I've been told that this would not be a high demand feature. So
> do I have a second vote? ;-)
The ability to have a dump that automatically separated the before-data
and after-data objects is definitely
useful. The amount of times I have had to dump the schema and data
separately just so I can modify the
schema before restore, or disable some function that is causing problems
can not even be counted.
Sincerely,
Joshua D. Drake
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2006-08-18 17:48:38 | Re: pg_dump schema breakup |
Previous Message | Naz Gassiep | 2006-08-18 17:33:03 | Re: pg_dump schema breakup |