From: | Harald Fuchs <hf517(at)protecting(dot)net> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: pg_dump bug fixing |
Date: | 2004-07-20 09:57:01 |
Message-ID: | pu7jszm26q.fsf@srv.protecting.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
In article <1090256502(dot)414(dot)17(dot)camel(at)jester>,
Rod Taylor <pg(at)rbt(dot)ca> writes:
> On Mon, 2004-07-19 at 12:36, Josh Berkus wrote:
>> Rod,
>>
>> > I think what we want is a clean template without all of the extras that
>> > template1 has.
>>
>> We have this, it's called Template0.
> Doesn't work for me. I remove a number of things that are included by
> default in template0, but yes, it's close.
I think pg_dump should do a kind of "diff" between template1 and the
database in question and include the necessary statements in the dump
to allow pg_restore to "replay" the diff after it has created the
database from template1.
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2004-07-20 10:22:33 | Re: Patch for pg_dump: Multiple -t options and new -T option |
Previous Message | Gaetano Mendola | 2004-07-20 09:49:31 | Re: localhost redux |