| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "anarazel(at)anarazel(dot)de" <andres(at)anarazel(dot)de> |
| Cc: | Andres Freund <andres(at)2ndquadrant(dot)com>, Paul Hinze <paul(dot)t(dot)hinze(at)gmail(dot)com>, pgsql-admin(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [ADMIN] Simultaneous index creates on different schemas cause deadlock? |
| Date: | 2013-04-25 19:54:55 |
| Message-ID: | 17038.1366919695@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-hackers |
"anarazel(at)anarazel(dot)de" <andres(at)anarazel(dot)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 the waiting 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Strahinja Kustudić | 2013-04-25 22:45:49 | Re: archive falling behind |
| Previous Message | anarazel@anarazel.de | 2013-04-25 18:57:43 | Re: [ADMIN] Simultaneous index creates on different schemas cause deadlock? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Timothy Garnett | 2013-04-25 20:01:38 | Re: Allowing parallel pg_restore from pipe |
| Previous Message | Heikki Linnakangas | 2013-04-25 19:34:42 | Re: Failing start-up archive recovery at Standby mode in PG9.2.4 |