From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
Cc: | Merlin Moncure <mmoncure(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: collateral benefits of a crash-safe visibility map |
Date: | 2011-05-10 17:51:59 |
Message-ID: | BANLkTi=ReSO0aJg=wzd0YUq5oZAzOt+qKg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, May 10, 2011 at 1:49 PM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> On Tue, May 10, 2011 at 6:02 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>> On Tue, May 10, 2011 at 12:57 PM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
>>> Hmmm, do we really need to WAL log freezing?
>>>
>>> Can we break down freezing into a 2 stage process, so that we can have
>>> first stage as a lossy operation and a second stage that is WAL
>>> logged?
>>
>> That might solve the relfrozenxid problem - set the bits in the heap,
>> sync the heap, then update relfrozenxid once the heap is guaranteed
>> safely on disk - but it again seems problematic for Hot Standby.
>
> How about we truncate the clog differently on each server? We could
> have a special kind of VACUUM that runs during Hot Standby, setting
> frozen hint bits only.
Interesting idea. It does seem complicated.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2011-05-10 17:52:10 | Re: 4.1beta1: ANYARRAY disallowed for DOMAIN types which happen to be arrays |
Previous Message | Simon Riggs | 2011-05-10 17:49:50 | Re: collateral benefits of a crash-safe visibility map |