Re: pg_dump bug fixing

From: Bruno Wolff III <bruno(at)wolff(dot)to>
To: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_dump bug fixing
Date: 2004-07-18 11:15:34
Message-ID: 20040718111534.GB31547@wolff.to
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Jul 18, 2004 at 14:33:09 +0800,
Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> wrote:
>
> * If you drop your public schema, a drop command is not issued for it in
> the dump, so when you restore your public schema is back

I am not sure that is really a bug. If someone really wants less than
what is in template1, they should be dropping stuff from template1
before recreating the database.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Christopher Kings-Lynne 2004-07-18 11:42:09 Re: pg_dump bug fixing
Previous Message Gaetano Mendola 2004-07-18 09:06:19 Re: NT + deadlock intended behaviour ?