On Thu, 24 Jun 2004, Tom Lane wrote:
> Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> writes:
> >> When running pg_dump --clean against a server that doesn't have schemas
> >> the namespace is blank and ends up producing a dump full off things like:
> >> DROP TABLE "".tab;
> > Since the person is dumping using 7.5 pg_dump, presumably they will be
> > restoring to 7.5, and it should be:
> > DROP TABLE "public".tab;
> 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
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.
> I seem to recall that there was some reason for using "", but I don't
> recall what exactly.
It seems like the only possible reasons are deliberately making it fail or
just a lack of testing. There's no way it does anything useful.
In response to
pgsql-patches by date
|Next:||From: Simon Riggs||Date: 2004-06-24 20:44:02|
|Subject: Re: nested xacts and phantom Xids|
|Previous:||From: Tom Lane||Date: 2004-06-24 20:00:47|
|Subject: Re: Cancel/Kill backend functions -- docs |