From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
---|---|
To: | Jochen Erwied <jochen(at)pgsql-performance(dot)erwied(dot)eu> |
Cc: | Uwe Bartels <uwe(dot)bartels(at)gmail(dot)com>, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: buffercache/bgwriter |
Date: | 2011-03-23 15:36:53 |
Message-ID: | AANLkTikfBd5MSoYbftWcpn0TaXeb2VbcJW0uHcyNaHHn@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Wed, Mar 23, 2011 at 6:19 AM, Jochen Erwied
<jochen(at)pgsql-performance(dot)erwied(dot)eu> wrote:
> Wednesday, March 23, 2011, 1:51:31 PM you wrote:
>
> [rearranged for quoting]
>
>> background writer stats
>> checkpoints_timed | checkpoints_req | buffers_checkpoint | buffers_clean |
>> maxwritten_clean | buffers_backend | buffers_alloc
>> -------------------+-----------------+--------------------+---------------+------------------+-----------------+---------------
>> 3 | 0 | 99754 | 0
>> | 0 | 115307 | 246173
>> (1 row)
>
> buffers_clean = 0 ?!
>
>> But I don't understand how postgres is unable to fetch a free buffer.
>> Does any body have an idea?
>
> Somehow looks like the bgwriter is completely disabled. How are the
> relevant settings in your postgresql.conf?
I suspect the work load is entirely bulk inserts, and is using a
Buffer Access Strategy. By design, bulk inserts generally write out
their own buffers.
Cheers,
Jeff
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Janes | 2011-03-23 16:01:51 | Re: buffercache/bgwriter |
Previous Message | Uwe Bartels | 2011-03-23 15:26:04 | Re: buffercache/bgwriter |