Re: pg_dump --clean w/ <= 7.2 server

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Kris Jurka <books(at)ejurka(dot)com>
Cc: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, pgsql-patches(at)postgresql(dot)org
Subject: Re: pg_dump --clean w/ <= 7.2 server
Date: 2004-06-24 21:53:25
Message-ID: 28045.1088114005@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

Kris Jurka <books(at)ejurka(dot)com> writes:
>> Possibly the most correct solution is to assign the name "public" to the
>> dummy schema that pg_dump creates internally when talking to a pre-7.3
>> server.

> I was considering that they might want to restore the dump into another
> schema and that would be easier with an unqualified name. I don't really
> understand why the name needs to be fully qualified in the first place.

Because it's entirely too likely that you'll drop the wrong thing if you
issue an unqualified DROP.

regards, tom lane

In response to

Responses

Browse pgsql-patches by date

  From Date Subject
Next Message Dennis Bjorklund 2004-06-24 22:05:24 Add argument name to CREATE FUNCTION documentation
Previous Message Tom Lane 2004-06-24 21:16:32 Re: stderr & win32 admin check