pgsql: Fix logic to detect conflicts or blocks involving exclusive locks - Mailing list pgsql-committers

From adunstan@postgresql.org (Andrew Dunstan)
Subject pgsql: Fix logic to detect conflicts or blocks involving exclusive locks
Date
Msg-id 20090412210245.1D5057540F4@cvs.postgresql.org
Whole thread Raw
List 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)

pgsql-committers by date:

Previous
From: gsmet@pgfoundry.org (User Gsmet)
Date:
Subject: pgfouine - pgfouine: implemented a simple garbage collector mechanism
Next
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Make a copy-editing pass over the 8.4 release notes.