From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(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:49:50 |
Message-ID: | BANLkTimtiiPSF4WPAGsmvHc-dS=z_fLwkQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2011-05-10 17:51:59 | Re: collateral benefits of a crash-safe visibility map |
Previous Message | Robert Haas | 2011-05-10 17:47:26 | Re: 4.1beta1: ANYARRAY disallowed for DOMAIN types which happen to be arrays |