Re: very long updates very small tables - Mailing list pgsql-performance

From Kevin Grittner
Subject Re: very long updates very small tables
Date
Msg-id 4D931A0C020000250003BF80@gw.wicourts.gov
Whole thread Raw
In response to Re: very long updates very small tables  (Lars Feistner <feistner@uni-heidelberg.de>)
Responses Re: very long updates very small tables
List pgsql-performance
Lars Feistner <feistner@uni-heidelberg.de> wrote:
> On 03/29/2011 09:28 PM, Kevin Grittner wrote:
>> Lars Feistner<feistner@uni-heidelberg.de>  wrote:
>>
>>> The log tells me that certain update statements take sometimes
>>> about 3-10 minutes. But we are talking about updates on tables
>>> with 1000 to 10000 rows and updates that are supposed to update
>>> 1 row.
>>
>> The top possibilities that come to my mind are:

> [all eliminated as possibilities]

If you haven't already done so, you should probably turn on
checkpoint logging to see if this corresponds to checkpoint
activity.  If it does, you can try cranking up how aggressive your
background writer is, and perhaps limiting your shared_buffers to
something around the size of your RAID controller's BBU cache.  (I
hope you have a RAID controller with BBU cache configured for
write-back, anyway.)

-Kevin

pgsql-performance by date:

Previous
From: pasman pasmański
Date:
Subject: Re: very long updates very small tables
Next
From: "Strange, John W"
Date:
Subject: COPY with high # of clients, partitioned table locking issues?