| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| Cc: | Ryan Kelly <rpkelly22(at)gmail(dot)com>, tom Tom <tom(at)tomforb(dot)es>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #6629: Creating a gist index fails with "too many LWLocks taken" |
| Date: | 2012-05-11 13:56:25 |
| Message-ID: | CA+U5nM+QzrhLM9V2Lwk2zqDEbTjwN-Y8nT6=kMDWibBwyiW_gg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 11 May 2012 11:07, Heikki Linnakangas
<heikki(dot)linnakangas(at)enterprisedb(dot)com> wrote:
> 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?
What is the downside from having >100 slots for general use.
ISTM we should have 250 slots and log a warning if we ever hit 50 or more.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2012-05-11 14:11:36 | Re: BUG #6629: Creating a gist index fails with "too many LWLocks taken" |
| Previous Message | Tom Lane | 2012-05-11 13:52:57 | Re: BUG #6629: Creating a gist index fails with "too many LWLocks taken" |