Re: issue with pg_restore
От | Nigel Heron |
---|---|
Тема | Re: issue with pg_restore |
Дата | |
Msg-id | 4E321D19.9050701@psycode.com обсуждение исходный текст |
Ответ на | Re: issue with pg_restore (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: issue with pg_restore
|
Список | pgsql-general |
On 11-07-28 09:41 AM, Tom Lane wrote: > Adrian Klaver<adrian.klaver@gmail.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.
В списке pgsql-general по дате отправления: