Re: parallel pg_restore - WIP patch - Mailing list pgsql-hackers

From Tom Lane
Subject Re: parallel pg_restore - WIP patch
Date
Msg-id 9592.1222689983@sss.pgh.pa.us
Whole thread Raw
In response to Re: parallel pg_restore - WIP patch  (Stefan Kaltenbrunner <stefan@kaltenbrunner.cc>)
Responses Re: parallel pg_restore - WIP patch  (Andrew Dunstan <andrew@dunslane.net>)
List 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


pgsql-hackers by date:

Previous
From: Stefan Kaltenbrunner
Date:
Subject: Re: parallel pg_restore - WIP patch
Next
From: Tom Lane
Date:
Subject: Re: Proposal: move column defaults into pg_attribute along with attacl