Re: pg_dump bug fixing - Mailing list pgsql-hackers

From Rod Taylor
Subject Re: pg_dump bug fixing
Date
Msg-id 1090256502.414.17.camel@jester
Whole thread Raw
In response to Re: pg_dump bug fixing  (Josh Berkus <josh@agliodbs.com>)
Responses Re: pg_dump bug fixing  (Josh Berkus <josh@agliodbs.com>)
Re: pg_dump bug fixing  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
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.

> Actually, KL, that would solve a lot of these duplicate object problems.  What 
> if pg_restore used Template0 and not Template1?    It wouldn't fix the "drop 
> public schema" issue but it would solve the others.

Remove the public schema from template0, but leave it in template1. Have
pg_dump treat the public schema the same as all of the other ones.




pgsql-hackers by date:

Previous
From: Josh Berkus
Date:
Subject: Re: pg_dump bug fixing
Next
From: Josh Berkus
Date:
Subject: Re: pg_dump bug fixing