Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 32DA19FBA70 for ; Wed, 8 Aug 2007 17:46:57 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-maia, port 10024) with ESMTP id 63147-02 for ; Wed, 8 Aug 2007 17:46:50 -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 A4FBC9FB84F for ; Wed, 8 Aug 2007 17:46:53 -0300 (ADT) Received: by noel.decibel.org (Postfix, from userid 1001) id 5128F564D3; Wed, 8 Aug 2007 15:46:52 -0500 (CDT) Received: (hashcash-sendmail, from uid 1001); Wed, 8 Aug 2007 15:46:49 -0500 Date: Wed, 8 Aug 2007 15:46:49 -0500 From: Decibel! To: Nick Fankhauser Cc: pgsql-admin@postgresql.org Subject: Re: Specific questions about wraparound and vacuum Message-ID: <20070808204649.GQ20424@nasby.net> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="/8E7gjuj425jZz9t" Content-Disposition: inline In-Reply-To: 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:070808:nickf@doxpop.com::B5MGYz0Wmugt5LQW:0EwZQ X-Hashcash: 1:20:070808:pgsql-admin@postgresql.org::12jLZ4xMHXiWOC0i:00000000000 0000000000000000000000001RN6 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200708/86 X-Sequence-Number: 26417 --/8E7gjuj425jZz9t Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Aug 08, 2007 at 12:07:14PM -0400, Nick Fankhauser wrote: > 2) If a regular (non-full) vacuum will not reset the XID. Will a > dump/restore take care of wraparound? We have done this in the past for > space reclamation because we seem to be able to dump/restore more quickly > than we can do a full vacuum. If you're doing that you need to re-evaluate your vacuuming strategy and possibly your free space map settings. You should normally never need to use pg_dump(all) or vacuum full to reclaim space. If you've got the ability to take enough downtime to dump and restore, you should really use that opportunity to upgrade to a modern version, too. --=20 Decibel!, aka Jim Nasby decibel@decibel.org EnterpriseDB http://enterprisedb.com 512.569.9461 (cell) --/8E7gjuj425jZz9t Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.3 (FreeBSD) iD8DBQFGuiu5dO30qud8SkgRAsvdAKCu9N5IcOlqTqi9E7o+uG14ajNTgwCeKWlE zxTfKg01R8Rngb9ySyKcCjE= =s+4N -----END PGP SIGNATURE----- --/8E7gjuj425jZz9t--