Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 75EEA64FD25 for ; Sun, 14 Dec 2008 14:28:00 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 49916-03 for ; Sun, 14 Dec 2008 14:27:57 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from mailsrv1.zmi.at (mailsrv1.zmi.at [212.69.162.198]) by mail.postgresql.org (Postfix) with ESMTP id 16AB364FCCF for ; Sun, 14 Dec 2008 14:27:56 -0400 (AST) Received: from mailsrv.i.zmi.at (h081217054243.dyn.cm.kabsi.at [81.217.54.243]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mailsrv.i.zmi.at", Issuer "mailsrv.i.zmi.at" (not verified)) by mailsrv1.zmi.at (Postfix) with ESMTP id D44F1EA0 for ; Sun, 14 Dec 2008 19:28:08 +0100 (CET) Received: from saturn.localnet (saturn.i.zmi.at [10.0.0.2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mailsrv.i.zmi.at (Postfix) with ESMTPSA id 675868A6C for ; Sun, 14 Dec 2008 19:27:51 +0100 (CET) From: Michael Monnerie Organization: it-management http://it-management.at To: pgsql-admin@postgresql.org Subject: Re: What is VACUUM waiting for? Date: Sun, 14 Dec 2008 19:27:42 +0100 User-Agent: KMail/1.10.1 (Linux/2.6.27.8-ZMI; KDE/4.1.3; x86_64; ; ) References: <200812122355.25481@zmi.at> <4943C70C.9070307@zeut.net> In-Reply-To: <4943C70C.9070307@zeut.net> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1359517.A3l21TjySy"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200812141927.43106@zmi.at> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200812/111 X-Sequence-Number: 30944 --nextPart1359517.A3l21TjySy Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Samstag 13 Dezember 2008 Matthew T. O'Connor wrote: > Do you have any vacuum delay setting turned on? =A0Perhaps they are too > high? Oh, I didn't remember there were some for normal vacuum, just the=20 auto_vaccuum. vacuum_cost_delay =3D 250 vacuum_cost_page_hit =3D 1 vacuum_cost_page_miss =3D 10 vacuum_cost_page_dirty =3D 20 vacuum_cost_limit =3D 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 =3D 0 because it's only one DB here. Still, I'd like to understand what values=20 would be reasonable on a server with many DBs, as we have some. mfg zmi =2D-=20 // 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 --nextPart1359517.A3l21TjySy Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEABECAAYFAklFUB8ACgkQzhSR9xwSCbTqfQCfUqOZv+zBThXGgBgnkPTvdv1u 2eYAniWleu/X0MPVdKWau2tmE4NnbBWj =qhAR -----END PGP SIGNATURE----- --nextPart1359517.A3l21TjySy--