Re: BUG #6629: Creating a gist index fails with "too many LWLocks taken"
От | Simon Riggs |
---|---|
Тема | Re: BUG #6629: Creating a gist index fails with "too many LWLocks taken" |
Дата | |
Msg-id | CA+U5nMK29jWExz52_3QoetJLmO1+Gz9__3SjZG=4P3nFh1qPJg@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: BUG #6629: Creating a gist index fails with "too many LWLocks taken" (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>) |
Ответы |
Re: BUG #6629: Creating a gist index fails with "too many
LWLocks taken"
|
Список | 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 по дате отправления: