Received: from localhost (maia-3.hub.org [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 023319FC128 for ; Wed, 8 Aug 2007 13:34:17 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 09950-08 for ; Wed, 8 Aug 2007 13:34:12 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 3D60C9FC113 for ; Wed, 8 Aug 2007 13:34:13 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.1/8.14.1) with ESMTP id l78GY43Z002644; Wed, 8 Aug 2007 12:34:04 -0400 (EDT) To: "Nick Fankhauser" cc: pgsql-admin@postgresql.org Subject: Re: Specific questions about wraparound and vacuum In-reply-to: References: Comments: In-reply-to "Nick Fankhauser" message dated "Wed, 08 Aug 2007 12:07:14 -0400" Date: Wed, 08 Aug 2007 12:34:04 -0400 Message-ID: <2643.1186590844@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200708/81 X-Sequence-Number: 26412 "Nick Fankhauser" writes: > 1) Do we need to do a *full* vacuum or just a "lazy" vacuum to take care of > the xid wraparound issues? Lazy is sufficient --- as long as it's database-wide including the system catalogs (which means a superuser has to do it). > Or... is it the case that by one billion, the docs really mean 2^30 > (1073741824) ? 2^30. You appear to have executed a bit under 600000 transactions since vacuuming, so if that's three hours then you've got about 5000 hours until wraparound. > 4) The documentation implies that I need to vacuum *every* database, even if > I'm not using them all, so I vacuumed template1, but can't connect to > template0. Do I really need to vacuum databases where no transactions are > occurring? If so, how to I deal with template0? You don't need to touch frozen databases. This was discussed yesterday ... regards, tom lane