Re: pg_restore dependencies - Mailing list pgsql-hackers

From Tom Lane
Subject Re: pg_restore dependencies
Date
Msg-id 22120.1239372958@sss.pgh.pa.us
Whole thread Raw
In response to pg_restore dependencies  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: pg_restore dependencies  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
Andrew Dunstan <andrew@dunslane.net> writes:
> We still have a little work to do on dependencies in parallel 
> pg_restore. The current test compares the candidate's locking 
> dependencies with those of the running jobs, and allows the candidate is 
> there isn't a match. That's not a broad enough test. The candidate will 
> block if there's a currently running CREATE INDEX command on the table, 
> for example, even though that doesn't require an exclusive lock. That's 
> not catastrophic, in that the restore doesn't fail, but it's fairly bad 
> because it reduces the achievable parallelism. Josh Berkus observed this 
> during testing on a very large restore.

Well, we certainly want to be able to run CREATE INDEXes in parallel,
so this would appear to require hard-wiring some conception of shared
versus exclusive lock into pg_restore.  I think it might be a bit late
to consider that for 8.4.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Guillaume Smet
Date:
Subject: Re: New trigger option of pg_standby
Next
From: Michael Renner
Date:
Subject: Re: Documentation Update: WAL & Checkpoints