Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id B5E5E9FBECC for ; Wed, 8 Aug 2007 23:16:38 -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 16935-06 for ; Wed, 8 Aug 2007 23:16:29 -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 A02519FBD8A for ; Wed, 8 Aug 2007 23:16:35 -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 l792GPDN012069; Wed, 8 Aug 2007 22:16:25 -0400 (EDT) To: "Nick Fankhauser" cc: pgsql-admin@postgresql.org Subject: Re: Specific questions about wraparound and vacuum In-reply-to: References: <11659.1186623487@sss.pgh.pa.us> Comments: In-reply-to "Nick Fankhauser" message dated "Wed, 08 Aug 2007 22:10:23 -0400" Date: Wed, 08 Aug 2007 22:16:25 -0400 Message-ID: <12068.1186625785@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200708/92 X-Sequence-Number: 26423 "Nick Fankhauser" writes: > On 8/8/07, Tom Lane wrote: >> 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 ... > They do change the values- I noted this by selecting age(datfrozenxid) > in template1 both before and after vacuuming and noting the change. Uh, that proves very little, because age() is a moving target. Did the raw datfrozenxid column values change? > Our regular vacuum process only runs on our single "prod" database- > not template1. Is template1 a "frozen" database, or just template0? template1 is not frozen in a standard installation. Basically you gotta vacuum everything that has datallowconn = true. regards, tom lane