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: "Greg Stark" <greg(dot)stark(at)enterprisedb(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:42:40
Message-ID: 36e682920810021042y63c4180ev58d6a59ed8a7047d@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
> It's not the buffeting it's the checksum. The problem arises if a page is
> read in but no wal logged modifications are done against it. If a hint bit
> is modified it won't be wal logged but the page is marked dirty.

Ahhhhh.  Thanks Greg.  Let me look into this a bit before I respond :)

-- 
Jonah H. Harris, Senior DBA
myYearbook.com

In response to

Responses

pgsql-hackers by date

Next:From: Alvaro HerreraDate: 2008-10-02 17:44:00
Subject: Re: Block-level CRC checks
Previous:From: Bruce MomjianDate: 2008-10-02 17:38:06
Subject: Re: Block-level CRC checks

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