pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Carlo Stonebanks <stonec.register@sympatico.ca>
To: pgsql-performance@postgresql.org
Subject: Re: Massive table (500M rows) update nightmare
Date: Thu, 14 Jan 2010 14:20:30 -0500
Message-ID: <hinqok$1ono$1@news.hub.org> (raw)
In-Reply-To: <dcc563d11001071740q572cdae2re410788fe790dbf6@mail.gmail.com>
References: <hi41os$eiv$1@news.hub.org>
	<b1b9fac61001071305vf182f3ajff6827f92c943c68@mail.gmail.com>
	<hi5kpr$184c$1@news.hub.org>
	<dcc563d11001071740q572cdae2re410788fe790dbf6@mail.gmail.com>

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.marlowe@gmail.com> wrote in message 
news:dcc563d11001071740q572cdae2re410788fe790dbf6@mail.gmail.com...
> 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?
>
> -- 
> Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-performance
> 




view thread (30+ messages)  latest in thread

Message-ID: <hinqok$1ono$1@news.hub.org>
Permalink:  ../hinqok$1ono$1@news.hub.org/
Also on:    postgresql.org/message-id/hinqok$1ono$1@news.hub.org

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: stonec.register@sympatico.ca
  Subject: Re: Massive table (500M rows) update nightmare
  In-Reply-To: <hinqok$1ono$1@news.hub.org>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox