Re: preserving forensic information when we freeze

From: Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Andres Freund <andres(at)2ndquadrant(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: preserving forensic information when we freeze
Date: 2013-12-11 19:25:30
Message-ID: 52A8BC2A.2030505@vmware.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 12/11/2013 09:17 PM, Robert Haas wrote:
> On Thu, Nov 21, 2013 at 4:51 PM, Andres Freund <andres(at)2ndquadrant(dot)com> wrote:
>> On 2013-11-21 15:59:35 -0500, Robert Haas wrote:
>>> Separate patch, but yeah, something like that. If we have to mark the
>>> page all-visible, we might as well freeze it while we're there. We
>>> should think about how it interacts with Heikki's freeze-without-write
>>> patch though.
>>
>> Definitely separate yes. And I agree, it's partially moot if Heikki's
>> patch gets in, but I am not sure it will make it into 9.4. There seems
>> to be quite some work left.
>
> I haven't heard anything further from Heikki, so I'm thinking we
> should proceed with this approach.

+1. It seems unlikely that my patch is going to make it into 9.4.

- Heikki

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2013-12-11 19:29:53 Re: -d option for pg_isready is broken
Previous Message Robert Haas 2013-12-11 19:19:40 Re: -d option for pg_isready is broken