From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | rod(at)iol(dot)ie |
Cc: | miller392(at)yahoo(dot)com, pgsql-general(at)postgresql(dot)org |
Subject: | Re: possible pg_dump bug |
Date: | 2009-01-28 17:39:05 |
Message-ID: | 19027.1233164345@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
"Raymond O'Donnell" <rod(at)iol(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Brian Witt | 2009-01-28 17:57:15 | use log_statement to log only SELECTs? |
Previous Message | Joao Ferreira gmail | 2009-01-28 17:19:16 | Re: possible pg_dump bug |