Re: Freezing is not WAL-logged

From: "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: Freezing is not WAL-logged
Date: 2006-10-19 20:29:51
Message-ID: 4537E03F.9060606@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Tom Lane wrote:
> "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com> writes:
>> I just noticed that freezing a tuple (in vacuumlazy.c) is not
>> WAL-logged.
>
> The theory is that this doesn't matter because the tuple is committed
> either way ... it's equivalent to a hint-bit update which we don't
> WAL-log either.

Because the relminxid-update is WAL-logged, you can get into situation
where relminxid > the real smallest xid of the table, as demonstrated by
the example I gave. relminxid is used to determine the safe clog cut-off
point, so that's not harmless.

Granted, the chances of getting data corruption from this are small, but
it's possible.

--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Jim C. Nasby 2006-10-20 05:27:21 Re: hello
Previous Message Alvaro Herrera 2006-10-19 19:22:04 Re: Freezing is not WAL-logged