Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 1BA6C9FC0BF for ; Wed, 8 Aug 2007 23:51:11 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024) with ESMTP id 64802-02 for ; Wed, 8 Aug 2007 23:51:00 -0300 (ADT) X-Greylist: delayed 00:55:09.679109 by SQLgrey-1.7.5 Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.170]) by postgresql.org (Postfix) with ESMTP id 165BA9FBFAB for ; Wed, 8 Aug 2007 23:51:05 -0300 (ADT) Received: by ug-out-1314.google.com with SMTP id a2so334339ugf for ; Wed, 08 Aug 2007 19:51:03 -0700 (PDT) Received: by 10.78.204.1 with SMTP id b1mr664510hug.1186624554089; Wed, 08 Aug 2007 18:55:54 -0700 (PDT) Received: by 10.78.178.20 with HTTP; Wed, 8 Aug 2007 18:55:54 -0700 (PDT) Message-ID: Date: Wed, 8 Aug 2007 21:55:54 -0400 From: "Nick Fankhauser" To: Decibel! Subject: Re: Specific questions about wraparound and vacuum Cc: pgsql-admin@postgresql.org In-Reply-To: <20070808204649.GQ20424@nasby.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20070808204649.GQ20424@nasby.net> X-Google-Sender-Auth: 2260a54b60e6ac5c X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200708/98 X-Sequence-Number: 26429 Thanks, both Tom and Jim for the information. That's exactly what I needed to know. Jim- We did in fact just increase the fsm values significantly based on the feedback we were getting from the vacuum messages. We do nightly non-full vacuums. Am I to understand that if we increase our fsm allocation to a sufficient size, we should not be losing any space? The "modern version" upgrade is on our wish list, but as it's a production system incorporating many technologies, we've had priorities elsewhere for a while, and 7.4 has been so darn stable and productive that the only motivation to move forward is so I don't have to feel ashamed to admit how far back we are. On the bright side, it's an indication of how good postgresql is that a growing business has had no issues with a quite old version. Regards, -Nick On 8/8/07, Decibel! wrote: > 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. > -- > Decibel!, aka Jim Nasby decibel@decibel.org > EnterpriseDB http://enterprisedb.com 512.569.9461 (cell) > > -- ------------------------------------------------------------------ Nick Fankhauser nickf@doxpop.com http://www.doxpop.com 765.965.7363 765.962.9788 (Fax) Doxpop - Public Records at Your Fingertips.