From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Freezing without write I/O |
Date: | 2013-06-01 20:21:36 |
Message-ID: | CA+TgmoYeosoz0r7+Zf8PrsunH1cU=7bRpRKakQqUzTc7b7H_3A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sat, Jun 1, 2013 at 2:48 PM, Heikki Linnakangas
<hlinnakangas(at)vmware(dot)com> wrote:
>> We define a new page-level bit, something like PD_RECENTLY_FROZEN.
>> When this bit is set, it means there are no unfrozen tuples on the
>> page with XIDs that predate the current half-epoch. Whenever we know
>> this to be true, we set the bit. If the page LSN crosses more than
>> one half-epoch boundary at a time, we freeze the page and set the bit.
>> If the page LSN crosses exactly one half-epoch boundary, then (1) if
>> the bit is set, we clear it and (2) if the bit is not set, we freeze
>> the page and set the bit.
>
> Yep, I think that would work. Want to write the patch, or should I? ;-)
Have at it. I think the tricky part is going to be figuring out the
synchronization around half-epoch boundaries.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2013-06-01 20:26:20 | Re: Freezing without write I/O |
Previous Message | Simon Riggs | 2013-06-01 19:22:56 | Re: Freezing without write I/O |