Horton

Re: parallel pg_restore - WIP patch

Tom Lane <tgl@sss.pgh.pa.us>

View thread
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Stefan Kaltenbrunner <stefan@kaltenbrunner.cc>
Cc: Andrew Dunstan <andrew@dunslane.net>, Russell Smith <mr-russ@pws.com.au>, PostgreSQL-development <pgsql-hackers@postgresql.org>, Jeffrey Baker <jwbaker@gmail.com>
Date: 2008-09-29T12:06:23Z
Lists: pgsql-hackers 
Stefan Kaltenbrunner <stefan@kaltenbrunner.cc> writes:
> pg_restore: [archiver (db)] could not execute query: ERROR:  deadlock 
> detected
> DETAIL:  Process 18100 waits for AccessExclusiveLock on relation 
> 1460818342 of database 1460815284; blocked by process 18103.
> Process 18103 waits for AccessExclusiveLock on relation 1460818336 of 
> database 1460815284; blocked by process 18100.
> HINT:  See server log for query details.

> ALTER TABLE ONLY foo
>      ADD CONSTRAINT fk_av_relations_av FOREIGN KEY (vs_id) REFERENCES 
> bar ...

Hmm, I'll bet the restore code doesn't realize that this can't run in
parallel with index creation on either table ...

			regards, tom lane