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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Olleg Samoylov <olleg(at)mipt(dot)ru>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #2239: "vacuumdb -a" remove freeze
Date: 2006-02-07 15:09:41
Message-ID: 6936.1139324981@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Olleg Samoylov <olleg(at)mipt(dot)ru> writes:
> IMHO "vacuumdb -a" must don't vacuum database with
> datvacuumxid=datfrozenxid.

That's not going to work because it will fail to detect whether the
database has been modified since the VACUUM FREEZE command.

In any case, what's the point? As long as you have a routine vacuuming
process in place, it doesn't really matter whether template1 gets
scanned. The only reason VACUUM FREEZE exists at all is to make it
possible to have a non-connectable, non-vacuumable template0.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Alfranio Correia Junior 2006-02-07 17:51:33 vacuum segmentation fault
Previous Message Tom Lane 2006-02-07 14:49:29 Re: BUG #2242: Inconsistent casting in query with literal vs query with parameter