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

Re: could not read block 77 of relation 1663/16385/388818775

From: John R Pierce <pierce(at)hogranch(dot)com>
To: pgsql-bugs(at)postgresql(dot)org
Subject: Re: could not read block 77 of relation 1663/16385/388818775
Date: 2008-11-24 17:20:13
Message-ID: 492AE24D.7090107@hogranch.com (view raw or flat)
Thread:
Lists: pgsql-bugs
Alexandra Nitzschke wrote:
> BTW... how about a block checksum that is checked just before writing 
> a block and just after reading it? I know this would degrade 
> performance, but I think we can afford that. Would it be possible to 
> incorporate such code without having to do too much patching?


oracle has had an option for some time that uses read/only page 
protection for each page of the shared buffer area...   when oracle 
knows it wants to modify a page, it un-protects it via a system 
call.     this catches any wild writes into the shared buffer area as a 
memory protection fault.

In response to

Responses

pgsql-bugs by date

Next:From: Barry ReddyDate: 2008-11-24 21:37:02
Subject: BUG #4548: Documentation Contradiction for 8.3
Previous:From: Alexandra NitzschkeDate: 2008-11-24 16:55:14
Subject: Re: could not read block 77 of relation 1663/16385/388818775

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