Re: [HACKERS] Simultaneous index creates on different schemas cause deadlock? - Mailing list pgsql-admin

From Tom Lane
Subject Re: [HACKERS] Simultaneous index creates on different schemas cause deadlock?
Date
Msg-id 17038.1366919695@sss.pgh.pa.us
Whole thread Raw
In response to Re: [HACKERS] Simultaneous index creates on different schemas cause deadlock?  ("anarazel@anarazel.de" <andres@anarazel.de>)
List pgsql-admin
"anarazel@anarazel.de" <andres@anarazel.de> writes:
> I don't have access to the code ATM an I wonder whether DROP CONCURRENTLY has a similar problem? Depends a bit on how
thewaiting is done... 

It's not a problem --- that code doesn't depend on waiting for snapshots
to expire, it just checks for other sessions holding locks on the target
table.  (I also did some experimental testing to verify this.)

            regards, tom lane


pgsql-admin by date:

Previous
From: "anarazel@anarazel.de"
Date:
Subject: Re: [HACKERS] Simultaneous index creates on different schemas cause deadlock?
Next
From: Strahinja Kustudić
Date:
Subject: Re: archive falling behind