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

Re: Block-level CRC checks

From: "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com>
To: "Gregory Stark" <stark(at)enterprisedb(dot)com>
Cc: "Brian Hurt" <bhurt(at)janestcapital(dot)com>, "Aidan Van Dyk" <aidan(at)highrise(dot)ca>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql(at)mohawksoft(dot)com, "Hannu Krosing" <hannu(at)2ndquadrant(dot)com>, Decibel! <decibel(at)decibel(dot)org>, "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>, "Pg Hackers" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Block-level CRC checks
Date: 2008-10-02 13:46:39
Message-ID: (view raw or whole thread)
Lists: pgsql-hackers
On Thu, Oct 2, 2008 at 9:42 AM, Gregory Stark <stark(at)enterprisedb(dot)com> wrote:
> It's even worse than that. Two processes can both be fiddling hint bits on
> different tuples (or even the same tuple) at the same time.

Agreed.  Back to the double-buffer idea, we could have a temporary
BLCKSZ buffer we could use immediately before write() which we could
copy the block to, perform the checksum on, and write out... is that
what you were thinking Tom?

Jonah H. Harris, Senior DBA

In response to

pgsql-hackers by date

Next:From: Heikki LinnakangasDate: 2008-10-02 13:50:07
Subject: Re: Block-level CRC checks
Previous:From: Jonah H. HarrisDate: 2008-10-02 13:45:02
Subject: Re: Block-level CRC checks

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