Re: CLOG contention, part 2 - Mailing list pgsql-hackers

From Robert Haas
Subject Re: CLOG contention, part 2
Date
Msg-id CA+TgmoYdwNQJQ31wiWiZPodVCO-9CqyiOz3W_r8b549JsPfiXQ@mail.gmail.com
Whole thread Raw
In response to Re: CLOG contention, part 2  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: CLOG contention, part 2
List pgsql-hackers
On Fri, Jan 20, 2012 at 10:44 AM, Robert Haas <robertmhaas@gmail.com> wrote:
>>> D'oh.  You're right.  Looks like I accidentally tried to apply this to
>>> the 9.1 sources.  Sigh...
>>
>> No worries. It's Friday.

Server passed 'make check' with this patch, but when I tried to fire
it up for some test runs, it fell over with:

FATAL:  no more LWLockIds available

I assume that it must be dependent on the config settings used.  Here are mine:

shared_buffers = 8GB
maintenance_work_mem = 1GB
synchronous_commit = off
checkpoint_segments = 300
checkpoint_timeout = 15min
checkpoint_completion_target = 0.9
wal_writer_delay = 20ms

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: pg_dump custom format specification
Next
From: Simon Riggs
Date:
Subject: Re: Should I implement DROP INDEX CONCURRENTLY?