pgsql: Fix pg_restore so parallel restore doesn't fail when the input - Mailing list pgsql-committers

From tgl@postgresql.org (Tom Lane)
Subject pgsql: Fix pg_restore so parallel restore doesn't fail when the input
Date
Msg-id 20100627190724.7D0127541D4@cvs.postgresql.org
Whole thread Raw
List pgsql-committers
Log Message:
-----------
Fix pg_restore so parallel restore doesn't fail when the input file doesn't
contain data offsets (which it won't, if pg_dump thought its output wasn't
seekable).  To do that, remove an unnecessarily aggressive error check, and
instead fail if we get to the end of the archive without finding the desired
data item.  Also improve the error message to be more specific about the
cause of the problem.  Per discussion of recent report from Igor Neyman.

Back-patch to 8.4 where parallel restore was introduced.

Modified Files:
--------------
    pgsql/src/bin/pg_dump:
        pg_backup_custom.c (r1.44 -> r1.45)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/bin/pg_dump/pg_backup_custom.c?r1=1.44&r2=1.45)

pgsql-committers by date:

Previous
From: c2main@pgfoundry.org (User C2main)
Date:
Subject: slony1-ctl - slony-ctl: Continue work with add nodes
Next
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Fix pg_restore so parallel restore doesn't fail when the input