Re: Massive table (500M rows) update nightmare

Guys, I want to thank you for all of the advice - my client has just made a
surprise announcement that he would like to set start from scratch with a
new server, so I am afraid that all of this great advice has to be seen in
the context of whatever decision is made on that. I am out there,
hat-in-hand, looking for advice under the PERFORM post: "New server to
improve performance on our large and busy DB - advice?"

Thanks again!

Carlo

"Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> wrote in message
news:dcc563d11001071740q572cdae2re410788fe790dbf6(at)mail(dot)gmail(dot)com(dot)(dot)(dot)
> On Thu, Jan 7, 2010 at 2:48 PM, Carlo Stonebanks
> <stonec(dot)register(at)sympatico(dot)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?
>
> --
> Sent via pgsql-performance mailing list (pgsql-performance(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-performance
>