Re: crash-safe visibility map, take three - Mailing list pgsql-hackers

From Robert Haas
Subject Re: crash-safe visibility map, take three
Date
Msg-id AANLkTimMEgSXBnns7jbaYRsqOO3mZ2Lg940MQQMowOSs@mail.gmail.com
Whole thread Raw
In response to Re: crash-safe visibility map, take three  (Dimitri Fontaine <dimitri@2ndQuadrant.fr>)
List pgsql-hackers
On Thu, Dec 2, 2010 at 6:37 AM, Dimitri Fontaine <dimitri@2ndquadrant.fr> wrote:
> Robert Haas <robertmhaas@gmail.com> writes:
>> Or maybe I do.  One other thing I've been thinking about with regard
>> to hint bit updates is that we might choose to mark that are
>> hint-bit-updated as "untidy" rather than "dirty".  The background
>
> Please review archives, you'll find the idea discussed and some patches
> to implement it, by Simon. I suppose you could begin here:
>
>  http://archives.postgresql.org/pgsql-patches/2008-06/msg00113.php

Thanks for the pointer.  I guess that demonstrates that good ideas
will keep floating back up to the surface.  It seems like the idea was
met with generally positive feedback, except that most people seemed
to want a slightly simpler system than what Simon was proposing.  I
suspect that this is mostly suffering from a lack of round tuits.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: "Kevin Grittner"
Date:
Subject: Re: V3: Idle in transaction cancellation
Next
From: Andres Freund
Date:
Subject: Re: V3: Idle in transaction cancellation