Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id 410E49FB53F for ; Sat, 28 Jul 2007 13:36:32 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024) with ESMTP id 11283-04 for ; Sat, 28 Jul 2007 13:36:29 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from noel.decibel.org (noel.decibel.org [67.100.216.10]) by postgresql.org (Postfix) with ESMTP id 6C0209FB4E1 for ; Sat, 28 Jul 2007 13:36:29 -0300 (ADT) Received: by noel.decibel.org (Postfix, from userid 1001) id 04A1556496; Sat, 28 Jul 2007 11:36:26 -0500 (CDT) Received: (hashcash-sendmail, from uid 1001); Sat, 28 Jul 2007 11:36:24 -0500 Date: Sat, 28 Jul 2007 11:36:24 -0500 From: "Jim C. Nasby" To: Steven Flatt Cc: pgsql-performance@postgresql.org Subject: Re: Vacuum looping? Message-ID: <20070728163624.GI39272@nasby.net> References: <357fa7590707271432l709da359n68deea693d2c5fdf@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="QlMGl5G66NJfRa6E" Content-Disposition: inline In-Reply-To: <357fa7590707271432l709da359n68deea693d2c5fdf@mail.gmail.com> X-Operating-System: FreeBSD 6.1-RELEASE-p10 amd64 X-Distributed: Join the Effort! http://www.distributed.net User-Agent: Mutt/1.5.13 (2006-08-11) X-Hashcash: 1:20:070728:steven.flatt@gmail.com::e2LozGO4Cn2Zv5Bm:000000000000000 0000000000000000000000002aNy X-Hashcash: 1:20:070728:pgsql-performance@postgresql.org::2PrlQe0vh4ekMAsO:00000 0000000000000000000000001GUt X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200707/395 X-Sequence-Number: 26079 --QlMGl5G66NJfRa6E Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jul 27, 2007 at 05:32:11PM -0400, Steven Flatt wrote: > weren't convinced was doing anything), then start a manual vacuum with a > higher vacuum_cost_limit to get things cleaned up quicker. What are your vacuum_cost_* settings? If you set those too aggressively you'll be in big trouble. The second pass on the vacuum means that maintenance_work_memory isn't large enough. --=20 Jim Nasby decibel@decibel.org EnterpriseDB http://enterprisedb.com 512.569.9461 (cell) --QlMGl5G66NJfRa6E Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.3 (FreeBSD) iD8DBQFGq3CHdO30qud8SkgRAi3GAJ9YNzIfr0QQ+7OGDRltpWfqu/7pGgCff9q2 FbT8HqHaOiE2e1dh2TR5pYw= =Qf3V -----END PGP SIGNATURE----- --QlMGl5G66NJfRa6E--