From: Tom Lane <tgl@sss.pgh.pa.us>
To: Nick Fankhauser <nickf@doxpop.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Specific questions about wraparound and vacuum
Date: Wed, 08 Aug 2007 22:16:25 -0400
Message-ID: <12068.1186625785@sss.pgh.pa.us> (raw)
In-Reply-To: <bb2fe60f0708081910p531c7704tc5e7a1dfa344e8c3@mail.gmail.com>
References: <bb2fe60f0708080907x1d8aa6dct5aa3cb1e1ba15897@mail.gmail.com>
<bb2fe60f0708080920v44dfa90fp14d8b5867f73cc31@mail.gmail.com>
<11659.1186623487@sss.pgh.pa.us>
<bb2fe60f0708081910p531c7704tc5e7a1dfa344e8c3@mail.gmail.com>
"Nick Fankhauser" <nickf@doxpop.com> writes:
> On 8/8/07, Tom Lane <tgl@sss.pgh.pa.us> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, nickf@doxpop.com
Subject: Re: Specific questions about wraparound and vacuum
In-Reply-To: <12068.1186625785@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox