Skip site navigation (1) Skip section navigation (2)

Re: parallel pg_restore - WIP patch

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, Russell Smith <mr-russ(at)pws(dot)com(dot)au>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Jeffrey Baker <jwbaker(at)gmail(dot)com>
Subject: Re: parallel pg_restore - WIP patch
Date: 2008-09-29 12:06:23
Message-ID: 9592.1222689983@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)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

In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2008-09-29 12:28:15
Subject: Re: Proposal: move column defaults into pg_attribute along with attacl
Previous:From: Stefan KaltenbrunnerDate: 2008-09-29 11:55:03
Subject: Re: parallel pg_restore - WIP patch

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group