Re: possible pg_dump bug - Mailing list pgsql-general

From Asko Oja
Subject Re: possible pg_dump bug
Date
Msg-id ecd779860901282235v30b94304p539a456003600df6@mail.gmail.com
Whole thread Raw
In response to Re: possible pg_dump bug  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
Hi

For the record. Using search_path for schema name handling is most annoying feature of pg_dump for us. I have run into many cases where separating schema is inconvenient but don't seem to remember any upsides.

regards
Asko

On Wed, Jan 28, 2009 at 7:39 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
"Raymond O'Donnell" <rod@iol.ie> writes:
> On 28/01/2009 17:09, David Miller wrote:
>> Pg Dump does not include schema name on insert statement generated
>> from pg_dump with a -d option when exporting data for a particular
>> table using the -t <schema>.<table> in version 8.3. I believe this
>> same bug exists in 8.4 but have not confirmed it. I believe pg_dump
>> should have an option to retain schema information.

> From memory, I think it does include a "set search_path" statement near
> the beginning.

Quite.  There is no bug here unless loading the dump file puts something
in the wrong schema.  (Suppressing the schema name where possible is in
fact considered a feature not a bug, since it makes it simpler to
hand-edit the dump file at need.)

                       regards, tom lane

--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

pgsql-general by date:

Previous
From: "A. Kretschmer"
Date:
Subject: Re: Disabling FK for tables in Postgresql
Next
From: aws
Date:
Subject: Re: libpq binary format for contrib/cube type?