Re: wal_buffers

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Euler Taveira de Oliveira <euler(at)timbira(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: wal_buffers
Date: 2012-02-19 18:08:28
Message-ID: CA+TgmoYL6GsPdpBbjhfj8xeCLdXmFBZCW1s9ZGxDv+efj=E2dA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Feb 19, 2012 at 9:46 AM, Euler Taveira de Oliveira
<euler(at)timbira(dot)com> wrote:
> On 19-02-2012 02:24, Robert Haas wrote:
>> I have attached tps scatterplots.  The obvious conclusion appears to
>> be that, with only 16MB of wal_buffers, the buffer "wraps around" with
>> some regularity
>>
> Isn't it useful to print some messages on the log when we have "wrap around"?
> In this case, we have an idea that wal_buffers needs to be increased.

I was thinking about that. I think that what might be more useful
than a log message is a counter somewhere in shared memory. Logging
imposes a lot of overhead, which is exactly what we don't want here,
and the volume might be quite high on a system that is bumping up
against this problem. Of course then the question is... how would we
expose the counter value?

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2012-02-19 18:24:34 Re: pg_upgrade --logfile option documentation
Previous Message Pavel Stehule 2012-02-19 17:04:53 Re: pgsql: Improve pretty printing of viewdefs.