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

From Simon Riggs
Subject Re: crash-safe visibility map, take four
Date
Msg-id AANLkTi=nfHFf4VR-gSMNxaVwPzEJGwCGHZYxNW20ocoL@mail.gmail.com
Whole thread Raw
In response to Re: crash-safe visibility map, take four  (Jesper Krogh <jesper@krogh.cc>)
Responses Re: crash-safe visibility map, take four
List pgsql-hackers
On Wed, Mar 23, 2011 at 6:16 AM, Jesper Krogh <jesper@krogh.cc> wrote:
> On 2011-03-22 21:43, Robert Haas wrote:
>>
>> I took a crack at implementing the first approach described above,
>> which seems to be by far the simplest idea we've come up with to date.
>>  Patch attached.  It doesn't seem to be that complicated, which could
>> mean either that it's not that complicated or that I'm missing
>> something.  Feel free to point and snicker in the latter case.
>
> Looks simple, but there is now benefit...

Your tests and discussion remind me that I haven't yet seen any tests
that show that index-only scans would be useful for performance.

Everyone just seems to be assuming that they make a huge difference,
and that the difference is practically realisable in a common
workload.

Perhaps that's already been done and I just didn't notice?

--
 Simon Riggs                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services


pgsql-hackers by date:

Previous
From: Radosław Smogura
Date:
Subject: Re: 2nd Level Buffer Cache
Next
From: Stephen Frost
Date:
Subject: Re: Pre-set Hint bits/VACUUM FREEZE on data load..?