Nigel Heron 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.jul...@mehnle.net
>> Have you got standard_conforming_strings turned on?
> That must be it! I do have sta
On 11-07-28 09:41 AM, Tom Lane wrote:
Adrian Klaver 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
Adrian Klaver 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
>>
On Wednesday, July 27, 2011 9:19:38 pm Nigel Heron wrote:
> Hi list,
> I'm trying to restore a backup into a database with a new name
>
> the dump was done on a 8.4 server with:
> pg_dump -F c -f bakfile olddb
>
> i'm trying to restore it with:
> createdb newdb; pg_restore -v --jobs=4 --disable-t
Hi list,
I'm trying to restore a backup into a database with a new name
the dump was done on a 8.4 server with:
pg_dump -F c -f bakfile olddb
i'm trying to restore it with:
createdb newdb; pg_restore -v --jobs=4 --disable-triggers
--no-tablespaces --dbname=newdb bakfile
or even just:
createdb
