Re: Massive table (500M rows) update nightmare - Mailing list pgsql-performance

From Scott Marlowe
Subject Re: Massive table (500M rows) update nightmare
Date
Msg-id dcc563d11001071740q572cdae2re410788fe790dbf6@mail.gmail.com
Whole thread Raw
In response to Re: Massive table (500M rows) update nightmare  ("Carlo Stonebanks" <stonec.register@sympatico.ca>)
Responses Re: Massive table (500M rows) update nightmare
New server to improve performance on our large and busy DB - advice?
Re: Massive table (500M rows) update nightmare
List pgsql-performance
On Thu, Jan 7, 2010 at 2:48 PM, Carlo Stonebanks
<stonec.register@sympatico.ca> wrote:
> Doing the updates in smaller chunks resolved these apparent freezes - or,
> more specifically, when the application DID freeze, it didn't do it for more
> than 30 seconds. In all likelyhood, this is the OS and the DB thrashing.

It might well be checkpoints.  Have you tried cranking up checkpoint
segments to something like 100 or more and seeing how it behaves then?

pgsql-performance by date:

Previous
From: Greg Smith
Date:
Subject: Re: Air-traffic benchmark
Next
From: Scott Marlowe
Date:
Subject: Re: "large" spam tables and performance: postgres memory parameters