From: Michael Monnerie <michael.monnerie@is.it-management.at>
To: pgsql-admin@postgresql.org
Subject: Re: Vacuum wait time problem
Date: Sat, 14 Feb 2009 01:02:09 +0100
Message-ID: <200902140102.09224@zmi.at> (raw)
In-Reply-To: <4995ABC0.4090401@musicreports.com>
References: <4995ABC0.4090401@musicreports.com>
On Freitag 13 Februar 2009 Roger Ging wrote:
> I'm running vacuum full analyze verbose on a table with 20million
> rows and 11 indexes. In top, I'm seeing [pdflush] and postgres:
> writer process each using diferent cpu cores, with wait time well
> above 90% on each of them. The vacuum has been running for several
> hours
Roger, I've had the same issue some time ago and wondered why it was so
slow. I did "iostat -kx 5 555" and saw that I/O was also quite low.
vacuum_cost_delay = 0
That was the trick for me. It was set to 250(ms), where it took 5 hours
for a vacuum to run. Now it takes 5-15 minutes.
And for your bloated table, you should also REINDEX afterwards, because
likely the index will be a mess also.
mfg zmi
--
// Michael Monnerie, Ing.BSc ----- http://it-management.at
// Tel: 0660 / 415 65 31 .network.your.ideas.
// PGP Key: "curl -s http://zmi.at/zmi.asc | gpg --import"
// Fingerprint: AC19 F9D5 36ED CD8A EF38 500E CE14 91F7 1C12 09B4
// Keyserver: wwwkeys.eu.pgp.net Key-ID: 1C1209B4
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-admin@postgresql.org
Cc: michael.monnerie@is.it-management.at
Subject: Re: Vacuum wait time problem
In-Reply-To: <200902140102.09224@zmi.at>
* 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