Skip site navigation (1) Skip section navigation (2)

Re: crash-safe visibility map, take three

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>
Cc: Jeff Davis <pgsql(at)j-davis(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: crash-safe visibility map, take three
Date: 2010-12-02 14:37:37
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
On Thu, Dec 2, 2010 at 6:37 AM, Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr> wrote:
> Robert Haas <robertmhaas(at)gmail(dot)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:

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
The Enterprise PostgreSQL Company

In response to

pgsql-hackers by date

Next:From: Andres FreundDate: 2010-12-02 14:57:18
Subject: Re: V3: Idle in transaction cancellation
Previous:From: Yeb HavingaDate: 2010-12-02 14:11:17
Subject: Re: FK's to refer to rows in inheritance child

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group