| From: | "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com> |
|---|---|
| To: | "Bruce Momjian" <bruce(at)momjian(dot)us> |
| 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:31:02 |
| Message-ID: | 36e682920810021031u83de61fpf80068136ded21dc@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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?
--
Jonah H. Harris, Senior DBA
myYearbook.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Stark | 2008-10-02 17:36:23 | Re: Block-level CRC checks |
| Previous Message | Aidan Van Dyk | 2008-10-02 17:19:16 | Re: Block-level CRC checks |