From: | Michael Monnerie <michael(dot)monnerie(at)is(dot)it-management(dot)at> |
---|---|
To: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: What is VACUUM waiting for? |
Date: | 2008-12-14 18:27:42 |
Message-ID: | 200812141927.43106@zmi.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Samstag 13 Dezember 2008 Matthew T. O'Connor wrote:
> Do you have any vacuum delay setting turned on? Perhaps they are too
> high?
Oh, I didn't remember there were some for normal vacuum, just the
auto_vaccuum.
vacuum_cost_delay = 250
vacuum_cost_page_hit = 1
vacuum_cost_page_miss = 10
vacuum_cost_page_dirty = 20
vacuum_cost_limit = 1000
Are those values to high/low? What should one use?
I think I will disable it at this one server, setting
vacuum_cost_delay = 0
because it's only one DB here. Still, I'd like to understand what values
would be reasonable on a server with many DBs, as we have some.
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: www.keyserver.net Key-ID: 1C1209B4
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Marlowe | 2008-12-14 18:32:16 | Re: What is VACUUM waiting for? |
Previous Message | paulo matadr | 2008-12-14 15:39:21 | Urgente error in restore prod |