On Tue, Jan 6, 2009 at 4:32 PM, Tom Lane <t...@sss.pgh.pa.us> wrote: > Andrew Dunstan <and...@dunslane.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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
