pgsql: Fix logic to detect conflicts or blocks involving exclusive locks

From: adunstan(at)postgresql(dot)org (Andrew Dunstan)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Fix logic to detect conflicts or blocks involving exclusive locks
Date: 2009-04-12 21:02:45
Message-ID: 20090412210245.1D5057540F4@cvs.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Log Message:
-----------
Fix logic to detect conflicts or blocks involving exclusive locks in parallel restore items.
If a currently running item needs an exclusive lock on any item that the candidate items needs
any sort of lock on, or vice versa, then the candidate item is not allowed to run now, and
must wait till later.

Modified Files:
--------------
pgsql/src/bin/pg_dump:
pg_backup_archiver.c (r1.169 -> r1.170)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/bin/pg_dump/pg_backup_archiver.c?r1=1.169&r2=1.170)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2009-04-13 06:05:13 pgsql: Make a copy-editing pass over the 8.4 release notes.
Previous Message User Gsmet 2009-04-12 12:55:40 pgfouine - pgfouine: implemented a simple garbage collector mechanism