From: | Nigel Heron <nigel(at)psycode(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Subject: | Re: issue with pg_restore |
Date: | 2011-07-29 02:38:17 |
Message-ID: | 4E321D19.9050701@psycode.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 11-07-28 09:41 AM, Tom Lane wrote:
> Adrian Klaver<adrian(dot)klaver(at)gmail(dot)com> writes:
>> On Wednesday, July 27, 2011 9:19:38 pm Nigel Heron wrote:
>>> I'm trying to restore a backup into a database with a new name
>>> It doesn't work .. pg_restore claims to be creating tables, indexes,
>>> etc. and there are no errors in the output. It only takes a few seconds
>>> to run (the file is ~250MB).
>> You running the pg_restore as postgres user with sufficient privileges?
yes, i'm running it as the postgres superuser
> I'm wondering if it could be the same bug reported two days ago:
> http://archives.postgresql.org/message-id/201107270042.22427.julian@mehnle.net
> Have you got standard_conforming_strings turned on?
>
> regards, tom lane
That must be it! I do have standard_conforming_strings on. What i found
is a string ending with a backslash as a default in a column definition
.. so that bug must be more wide spread than just comments.
eg.
CREATE TABLE foo ( bar text DEFAULT '.\somepath\' );
thanks,
-nigel.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2011-07-29 02:50:54 | Re: issue with pg_restore |
Previous Message | Adrian Klaver | 2011-07-29 02:20:47 | Re: I'm in the depths of a CAST nightmare and I can't work my out |