| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Nigel Heron <nigel(at)psycode(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: issue with pg_restore |
| Date: | 2011-07-29 02:50:54 |
| Message-ID: | 12178.1311907854@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Nigel Heron <nigel(at)psycode(dot)com> writes:
> On 11-07-28 09:41 AM, Tom Lane wrote:
>> 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?
> 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.
Yeah, actually it affects any situation where a string literal in the
SQL dump ends in a backslash. I've committed a patch for it, but in the
meantime the best workaround is to not use a direct-to-database restore,
but pipe the SQL output through psql.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2011-07-29 03:56:04 | Re: Fresh Restore - relation contains more than "max_fsm_pages" |
| Previous Message | Nigel Heron | 2011-07-29 02:38:17 | Re: issue with pg_restore |