Received: from localhost (maia-3.hub.org [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 4A31B9FB6AE for ; Wed, 8 Aug 2007 23:10:31 -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 89547-10 for ; Wed, 8 Aug 2007 23:10:18 -0300 (ADT) X-Greylist: delayed 00:07:50.4565 by SQLgrey-1.7.5 Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.191]) by postgresql.org (Postfix) with ESMTP id 2144A9FB69E for ; Wed, 8 Aug 2007 23:10:26 -0300 (ADT) Received: by nf-out-0910.google.com with SMTP id f5so99461nfh for ; Wed, 08 Aug 2007 19:10:24 -0700 (PDT) Received: by 10.78.204.1 with SMTP id b1mr667155hug.1186625423362; Wed, 08 Aug 2007 19:10:23 -0700 (PDT) Received: by 10.78.178.20 with HTTP; Wed, 8 Aug 2007 19:10:23 -0700 (PDT) Message-ID: Date: Wed, 8 Aug 2007 22:10:23 -0400 From: "Nick Fankhauser" To: pgsql-admin@postgresql.org Subject: Re: Specific questions about wraparound and vacuum In-Reply-To: <11659.1186623487@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <11659.1186623487@sss.pgh.pa.us> X-Google-Sender-Auth: 1669ea3bbc9e1874 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200708/90 X-Sequence-Number: 26421 On 8/8/07, Tom Lane wrote: > "Nick Fankhauser" writes: > > One other question- when I'm vacuuming, I always get the warning: > > > WARNING: some databases have not been vacuumed in transactions > > HINT: Better vacuum them within transactions, or you may > > have a wraparound failure. > > > I get these even after all DBs except template0 have been freshly vacuumed. Why? > > Do your vacuums change the pg_database.datfrozenxid values for the > databases? The only reason I can think of for them not to do so > is if you're not doing them as superuser ... > > regards, tom lane > They do change the values- I noted this by selecting age(datfrozenxid) in template1 both before and after vacuuming and noting the change. Also, the maintenance process that does the regular vacuum on our "prod" database is run as user postgres. Our regular vacuum process only runs on our single "prod" database- not template1. Is template1 a "frozen" database, or just template0? If template1 is not frozen, that may explain the warning. Would I get the warning even if the DB that has not been recently vacuumed has never had any transactions on it? -Nick -- ------------------------------------------------------------------ Nick Fankhauser nickf@doxpop.com http://www.doxpop.com 765.965.7363 765.962.9788 (Fax) Doxpop - Public Records at Your Fingertips.