Re: Specific questions about wraparound and vacuum

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Nick Fankhauser" <nickf(at)doxpop(dot)com>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: Specific questions about wraparound and vacuum
Date: 2007-08-09 02:16:25
Message-ID: 12068.1186625785@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

"Nick Fankhauser" <nickf(at)doxpop(dot)com> writes:
> On 8/8/07, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Michael Goldner 2007-08-09 02:22:50 Joining tables in two different databases?
Previous Message Jessica Richard 2007-08-09 02:15:08 Does Postgres 8.x support stored procedure?