From: | Bruno Wolff III <bruno(at)wolff(dot)to> |
---|---|
To: | Robert Fitzpatrick <robert(at)webtent(dot)com> |
Cc: | Doug McNaught <doug(at)mcnaught(dot)org>, PostgreSQL <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: DROP DATABASE, but still there |
Date: | 2004-11-11 20:10:06 |
Message-ID: | 20041111201006.GA30375@wolff.to |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, Nov 11, 2004 at 14:17:45 -0500,
Robert Fitzpatrick <robert(at)webtent(dot)com> wrote:
> On Thu, 2004-11-11 at 14:03, Doug McNaught wrote:
> > Robert Fitzpatrick <robert(at)webtent(dot)com> writes:
> >
> > > What does it mean when you drop a database and then recreate with the
> > > same name and all the objects are still there. I want to wipe out the db
> > > and put back from pg_restore. After I re-create the db, all the old
> > > tables are back before I run pg_restore.
> >
> > Check the 'template1' database to see if the tables got put in there
> > by mistake at some point.
>
> Yeah, I was just starting to realize that these objects that keep coming
> back are in the template1 as well.....any reason why I shouldn't drop
> the template1 and re-create like any other?
I think you need to use the -T option if you do this to have a copy made
of template0 instead of the default of template1.
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Stark | 2004-11-11 20:15:34 | Re: implicit casting problem |
Previous Message | Goutam Paruchuri | 2004-11-11 20:02:50 | Re: When to switch to Postgres 8.0? |