From: Leo Mannhart <leo.mannhart@beecom.ch>
To: pgsql-performance@postgresql.org
Subject: Re: Massive table (500M rows) update nightmare
Date: Thu, 07 Jan 2010 16:47:10 +0100
Message-ID: <4B4601FE.5010300@beecom.ch> (raw)
In-Reply-To: <4B45A6FE020000250002DEBC@gw.wicourts.gov>
References: <hi41os$eiv$1@news.hub.org>
<4B45DE4C.4050606@beecom.ch>
<4B45A6FE020000250002DEBC@gw.wicourts.gov>
Kevin Grittner wrote:
> Leo Mannhart <leo.mannhart@beecom.ch> wrote:
>
>> You could also try to just update the whole table in one go, it is
>> probably faster than you expect.
>
> That would, of course, bloat the table and indexes horribly. One
> advantage of the incremental approach is that there is a chance for
> autovacuum or scheduled vacuums to make space available for re-use
> by subsequent updates.
>
> -Kevin
>
ouch...
thanks for correcting this.
... and forgive an old man coming from Oracle ;)
Leo
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: leo.mannhart@beecom.ch
Subject: Re: Massive table (500M rows) update nightmare
In-Reply-To: <4B4601FE.5010300@beecom.ch>
* 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