Received: from localhost (maia-3.hub.org [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 4950E9FB6AE for ; Wed, 8 Aug 2007 22:38:23 -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 85926-09 for ; Wed, 8 Aug 2007 22:38: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 25AC59FB4F5 for ; Wed, 8 Aug 2007 22:38:20 -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 l791c7wN011660; Wed, 8 Aug 2007 21:38:08 -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:20:07 -0400" Date: Wed, 08 Aug 2007 21:38:07 -0400 Message-ID: <11659.1186623487@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200708/89 X-Sequence-Number: 26420 "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