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

Re: WAL logging freezing

From: "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-hackers(at)postgresql(dot)org>,<pgsql-patches(at)postgresql(dot)org>
Subject: Re: WAL logging freezing
Date: 2006-10-27 15:44:52
Message-ID: 45422974.6010109@enterprisedb.com (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
Tom Lane wrote:
> Heikki Linnakangas <heikki(at)enterprisedb(dot)com> writes:
>> I would've liked to give freezing a new opcode, 
>>   but we've ran out of them (see htup.h).
> 
> Hardly ... we have plenty of unused rmgr id's still.

Good point.

> The real issue that still has to be resolved is the interaction of all
> this stuff with PITR scenarios --- is it still safe to not log hint-bit
> updates when PITR is on?  I think it's premature to start writing
> patches until we've decided how this really needs to work.

Not logging hint-bit updates seems safe to me. As long as we have the 
clog, the hint-bit is just a hint. The problem with freezing is that 
after freezing tuples, the corresponding clog page can go away.

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

In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2006-10-27 16:01:12
Subject: Re: WAL logging freezing
Previous:From: Neil ConwayDate: 2006-10-27 15:10:59
Subject: Re: bug in on_error_rollback !?

pgsql-patches by date

Next:From: Tom LaneDate: 2006-10-27 16:01:12
Subject: Re: WAL logging freezing
Previous:From: Neil ConwayDate: 2006-10-27 14:56:43
Subject: Re: GUC description cleanup

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