| From: | Thomas Kellerer <spam_eater(at)gmx(dot)net> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: concurrent SELECT blocking ALTER? |
| Date: | 2014-01-29 22:51:00 |
| Message-ID: | lcc0jn$ve2$1@ger.gmane.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Neil Harkins wrote on 29.01.2014 23:37:
> I totally understand DDL taking exclusive locks, the problem here seems to be that the *SELECTs*
>are taking out exclusive locks, locking out the ALTER, which feels like a bug.
The SELECT is not holding an exclusive lock, it's holing a *shared* lock, but the ALTER is _requesting_ an exclusive lock and that can only be granted until all shared (or otherwise incompatible) locks are released.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Neil Harkins | 2014-01-29 23:09:30 | Re: concurrent SELECT blocking ALTER? |
| Previous Message | Neil Harkins | 2014-01-29 22:37:39 | Re: concurrent SELECT blocking ALTER? |