Re: Blocking excessively in FOR UPDATE - Mailing list pgsql-performance

From Claudio Freire
Subject Re: Blocking excessively in FOR UPDATE
Date
Msg-id CAGTBQpYo9=h03DRxK4pfGiF6hzEcuLAHLjhw24dZV+TUqZMyEg@mail.gmail.com
Whole thread Raw
In response to Re: Blocking excessively in FOR UPDATE  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Blocking excessively in FOR UPDATE  (Claudio Freire <klaussfreire@gmail.com>)
List pgsql-performance
On Fri, Nov 4, 2011 at 3:54 PM, Robert Haas <robertmhaas@gmail.com> wrote:
> On Fri, Nov 4, 2011 at 2:45 PM, Claudio Freire <klaussfreire@gmail.com> wrote:
>> I don't think 1 second can be such a big difference for the bgwriter,
>> but I might be wrong.
>
> Well, the default value is 200 ms.   And I've never before heard of
> anyone tuning it up, except maybe to save on power consumption on a
> system with very low utilization.  Nearly always you want to reduce
> it.

Will try

>> The wal_writer makes me doubt, though. If logged activity was higher
>> than 8MB/s, then that setting would block it all.
>> I guess I really should lower it.
>
> Here again, you've set it to ten times the default value.  That
> doesn't seem like a good idea.  I would start with the default and
> tune down.

Already did that. Waiting to see how it turns out.

pgsql-performance by date:

Previous
From: Shaun Thomas
Date:
Subject: Re: Blocking excessively in FOR UPDATE
Next
From: Heikki Linnakangas
Date:
Subject: Re: SSL encryption makes bytea transfer slow