From: | Neil Harkins <nharkins(at)gmail(dot)com> |
---|---|
To: | Thomas Kellerer <spam_eater(at)gmx(dot)net> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: concurrent SELECT blocking ALTER? |
Date: | 2014-01-29 23:09:30 |
Message-ID: | CAMtfGdXTv4UvcYNzsxW8M1j9jLOj-Yg6u-m8rz7vPOpDZDZq2Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Note the number of exclusive locks in my first message, it is equal to the
number of threads (20). Also, the ALTER was not running then, apologies if
that was not clear.
On Wednesday, January 29, 2014, Thomas Kellerer <spam_eater(at)gmx(dot)net> wrote:
> 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.
>
>
>
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Janes | 2014-01-29 23:33:16 | Re: concurrent SELECT blocking ALTER? |
Previous Message | Thomas Kellerer | 2014-01-29 22:51:00 | Re: concurrent SELECT blocking ALTER? |