Possible work-around for 9.1 partial vacuum bug?

From: Jim Nasby <jim(at)nasby(dot)net>
To: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Possible work-around for 9.1 partial vacuum bug?
Date: 2013-12-08 21:33:39
Message-ID: 52A4E5B3.6020400@nasby.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

If I'm understanding the vacuum truncate bug correctly, it can be avoided if every 2^31 transactions[1] you:

SET vacuum_freeze_table_age = 0;
VACUUM FREEZE;

table_age = 0 disables partial vacuum and then everything[1] gets frozen, eliminating the risk. Or am I missing something?

[1]: Obviously open transactions mean 2^31 isn't exact.
--
Jim C. Nasby, Data Architect jim(at)nasby(dot)net
512.569.9461 (cell) http://jim.nasby.net

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Mark Kirkwood 2013-12-08 22:19:48 Re: ANALYZE sampling is too good
Previous Message MauMau 2013-12-08 21:16:25 Re: [RFC] Shouldn't we remove annoying FATAL messages from server log?