Re: Block-level CRC checks

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: Aidan Van Dyk <aidan(at)highrise(dot)ca>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Martijn van Oosterhout <kleptog(at)svana(dot)org>, Greg Stark <greg(dot)stark(at)enterprisedb(dot)com>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Gregory Stark <stark(at)enterprisedb(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Block-level CRC checks
Date: 2008-11-18 17:59:16
Message-ID: 1227031156.7298.16.camel@jd-laptop.pragmaticzealot.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, 2008-11-18 at 12:54 -0500, Aidan Van Dyk wrote:
> * Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> [081118 12:43]:
> > Aidan Van Dyk <aidan(at)highrise(dot)ca> writes:

> > The trouble here is to avoid repeated WAL-logging of the same hint bits.
> >
> > (Alvaro's patch tried to do that by depending on another hint bit in the
> > page header, but that seems unsafe if hint bit setters aren't taking
> > exclusive lock.)
>
> And I know it's extra IO. That's why I started the whole thing with a question
> along the lines of "how much extra IO are people going to take" for the sake of
> "guarenteeing" we read exactly what we wrote.

Those that need it will turn it on, those that don't won't.

IO is cheap for those that are going to actually need this feature.

Joshua D. Drake

>
> a.
>
--

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2008-11-18 18:02:08 Re: is any reason why only one columns subselect are allowed in array()?
Previous Message Pavel Stehule 2008-11-18 17:55:26 Re: is any reason why only one columns subselect are allowed in array()?