pgsql: Actually, all of parallel restore's limitations should be tested - Mailing list pgsql-committers

From Tom Lane
Subject pgsql: Actually, all of parallel restore's limitations should be tested
Date
Msg-id E1Qxrbd-0002eu-PY@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Actually, all of parallel restore's limitations should be tested earlier.

On closer inspection, whining in restore_toc_entries_parallel is really
much too late for any user-facing error case.  The right place to do it
is at the start of RestoreArchive(), before we've done anything interesting
(suh as trying to DROP all the targets ...)

Back-patch to 8.4, where parallel restore was introduced.

Branch
------
REL9_0_STABLE

Details
-------
http://git.postgresql.org/pg/commitdiff/2de0fdeb68d7176df35a880c9180bd9e2d9eca4c

Modified Files
--------------
src/bin/pg_dump/pg_backup_archiver.c |   38 ++++++++++++++++++++-------------
1 files changed, 23 insertions(+), 15 deletions(-)


pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: pgsql: Actually, all of parallel restore's limitations should be tested
Next
From: Robert Haas
Date:
Subject: pgsql: Improve spinlock performance for HP-UX, ia64, non-gcc.