Re: CLOG contention - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: CLOG contention
Date
Msg-id CA+U5nMJyRJ8caNQhUN1TWaOPDfu4MQfDtF1e0V4f2d+DGHB5hw@mail.gmail.com
Whole thread Raw
In response to Re: CLOG contention  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: CLOG contention  (Robert Haas <robertmhaas@gmail.com>)
Re: CLOG contention  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-hackers
On Thu, Jan 5, 2012 at 7:12 PM, Robert Haas <robertmhaas@gmail.com> wrote:
> On Thu, Jan 5, 2012 at 11:10 AM, Simon Riggs <simon@2ndquadrant.com> wrote:
>> Let's commit the change to 32.
>
> I would like to do that, but I think we need to at least figure out a
> way to provide an escape hatch for people without much shared memory.
> We could do that, perhaps, by using a formula like this:
>
> 1 CLOG buffer per 128MB of shared_buffers, with a minimum of 8 and a
> maximum of 32

We're talking about an extra 192KB or thereabouts and Clog buffers
will only be the size of subtrans when we've finished.

If you want to have a special low-memory option, then it would need to
include many more things than clog buffers.

Let's just use a constant value for clog buffers until the low-memory
patch arrives.

--
 Simon Riggs                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: CLOG contention
Next
From: Robert Haas
Date:
Subject: Re: CLOG contention