Greg Stark <[EMAIL PROTECTED]> writes:
> Robert Fitzpatrick <[EMAIL PROTECTED]> writes:
>> 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?
> You can do t
Robert Fitzpatrick <[EMAIL PROTECTED]> writes:
> 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?
You can do that but you'll have to do:
CREATE DATABAS
On Thu, Nov 11, 2004 at 14:17:45 -0500,
Robert Fitzpatrick <[EMAIL PROTECTED]> wrote:
> On Thu, 2004-11-11 at 14:03, Doug McNaught wrote:
> > Robert Fitzpatrick <[EMAIL PROTECTED]> writes:
> >
> > > What does it mean when you drop a database and then recreate with the
> > > same name and all the
On Thu, 2004-11-11 at 14:03, Doug McNaught wrote:
> Robert Fitzpatrick <[EMAIL PROTECTED]> 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-c
Robert Fitzpatrick <[EMAIL PROTECTED]> 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_
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.
--
Robert
---(end o
