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

Re: Block-level CRC checks

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com>
Cc: Aidan Van Dyk <aidan(at)highrise(dot)ca>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Brian Hurt <bhurt(at)janestcapital(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Block-level CRC checks
Date: 2008-10-02 17:38:06
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Jonah H. Harris wrote:
> On Thu, Oct 2, 2008 at 1:07 PM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> >> If we're double-buffering the write, I don't see where we could be
> >> introducing a torn-page, as we'd actually be writing a copied version
> >> of the buffer.  Will look into this.
> >
> > The torn page is during kernel write to disk, I assume, so it is still
> > possible.
> Well, we can't really control too much of that.  The most common
> solution to that I've seen is to double-write the page (which some
> OSes already do regardless).  Or, are you meaning something else?

I just don't see how writing a copy of the page (rather than the
original) to the kernel affects issues about torn pages.

  Bruce Momjian  <bruce(at)momjian(dot)us>

  + If your life is a hard drive, Christ can be your backup. +

In response to

pgsql-hackers by date

Next:From: Jonah H. HarrisDate: 2008-10-02 17:42:40
Subject: Re: Block-level CRC checks
Previous:From: Greg StarkDate: 2008-10-02 17:36:23
Subject: Re: Block-level CRC checks

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