Re: BUG #6629: Creating a gist index fails with "too many LWLocks taken" - Mailing list pgsql-bugs

From Simon Riggs
Subject Re: BUG #6629: Creating a gist index fails with "too many LWLocks taken"
Date
Msg-id CA+U5nMK29jWExz52_3QoetJLmO1+Gz9__3SjZG=4P3nFh1qPJg@mail.gmail.com
Whole thread Raw
In response to Re: BUG #6629: Creating a gist index fails with "too many LWLocks taken"  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Responses Re: BUG #6629: Creating a gist index fails with "too many LWLocks taken"  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
List pgsql-bugs
On 11 May 2012 15:14, Heikki Linnakangas
<heikki.linnakangas@enterprisedb.com> wrote:
> On 11.05.2012 16:56, Simon Riggs wrote:
>>
>> On 11 May 2012 11:07, Heikki Linnakangas
>> <heikki.linnakangas@enterprisedb.com> =A0wrote:
>>
>>> I wonder if we should reserve a few of the lwlock "slots" for critical
>>> sections, to make this less likely to happen. Not only in this case, but
>>> in
>>> general. We haven't seen this problem often, but it would be quite
>>> trivial
>>> to reserve a few slots.
>>
>>
>> Why reserve them solely for critical sections?
>
>
> Because if you run out of lwlocks in a critical section, you get a PANIC.

Yes, but why reserve them solely for critical sections? If you have an
escape hatch you use it, always


--=20
=A0Simon Riggs=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 http:/=
/www.2ndQuadrant.com/
=A0PostgreSQL Development, 24x7 Support, Training & Services

pgsql-bugs by date:

Previous
From: Robert Haas
Date:
Subject: Re: BUG #6629: Creating a gist index fails with "too many LWLocks taken"
Next
From: Heikki Linnakangas
Date:
Subject: Re: BUG #6629: Creating a gist index fails with "too many LWLocks taken"