Skip site navigation (1) Skip section navigation (2)

Re: BUG #2239: "vacuumdb -a" remove freeze

From: Olleg Samoylov <olleg(at)mipt(dot)ru>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #2239: "vacuumdb -a" remove freeze
Date: 2006-02-07 07:36:46
Message-ID: 43E84E0E.5080605@mipt.ru (view raw or flat)
Thread:
Lists: pgsql-bugs
Tom Lane wrote:
> "Olleg Samoylov" <olleg_s(at)mail(dot)ru> writes:
> 
>> Opps, template1 must not be vacuumed.
> 
> 
> Says who?
> 
> If we didn't vacuum template1 then it would be subject to XID 
> wraparound problems, unless it had never been modified, which is 
> something vacuumdb can't count on.

template1 frozen by "vacuum freeze", thus can't be subject of XID
wraparound problems, isn't it?

man vacuum:
> If this is done when there are no other open transactions in the same
>  database, then  it  is  guaranteed  that  all  tuples in  the 
> database  are  ‘‘frozen’’  and  will  not  be subject to transaction 
> ID wraparound problems, no matter how long the database  is  left 
> unvacuumed.

IMHO "vacuumdb -a" must don't vacuum database with 
datvacuumxid=datfrozenxid.

-- 
Olleg Samoylov

In response to

Responses

pgsql-bugs by date

Next:From: KF TaiDate: 2006-02-07 08:19:39
Subject: BUG #2244: silent installation to set password never expires
Previous:From: Matej RizmanDate: 2006-02-07 02:41:03
Subject: BUG #2243: Postgresql fails to finish some queries

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group