Re: Vacuum wait time problem

From: Michael Monnerie <michael(dot)monnerie(at)is(dot)it-management(dot)at>
To: pgsql-admin(at)postgresql(dot)org
Subject: Re: Vacuum wait time problem
Date: 2009-02-14 00:02:09
Message-ID: 200902140102.09224@zmi.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

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

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Scott Marlowe 2009-02-14 01:08:12 Re: Vacuum wait time problem
Previous Message Scott Marlowe 2009-02-13 22:40:04 Re: Vacuum wait time problem