Re: parallel restore

From: "Jaime Casanova" <jcasanov(at)systemguards(dot)com(dot)ec>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Andrew Dunstan" <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: parallel restore
Date: 2009-01-06 22:43:49
Message-ID: 3073cc9b0901061443h3aece63eh73f3a4a182dbe5ef@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Jan 6, 2009 at 4:32 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
>> Jaime Casanova wrote:
>>> i'm using:
>>> pg_restore -f mic.backup -Fc -v -m5
>
>> Strange. Maybe the server log will show activity?
>
> There's no connection info, so that should just print to stdout, and
> probably there is no point in any parallelism. I'm guessing the -m
> switch invokes code that fails to deal with this case.
>

ah! ok, i run the command in this way instead:
pg_restore -p 54320 -Fc -v -d mic mic.backup (why i can't use -f?) and
it works fine, then to test parallel restore i did
pg_restore -p 54320 -Fc -v -m5 -d mic mic.backup
but i forgot to clean up the database... of course it throws a lot of
"$object_name already exists" messages and the last one was a little
strange, it says:

pg_restore: [archiver (db)] connection to database "public" failed:
FATAL: database "public" does not exist

but there isn't a "public" database in the backup...

besides that, maybe, unrelated issue, it seems to work fine...

--
Atentamente,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Asesoría y desarrollo de sistemas
Guayaquil - Ecuador
Cel. +59387171157

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jaime Casanova 2009-01-06 22:48:15 Re: parallel restore
Previous Message Tom Lane 2009-01-06 22:30:11 Re: hist boundary duplicates bug in head and 8.3