Re: Index corruption - Mailing list pgsql-hackers

From Marc Munro
Subject Re: Index corruption
Date
Msg-id 1151704966.3913.128.camel@bloodnok.com
Whole thread Raw
In response to Re: Index corruption  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Index corruption  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Thu, 2006-06-29 at 21:47 -0400, Tom Lane wrote:
> One easy thing that would be worth trying is to build with
> --enable-cassert and see if any Asserts get provoked during the

> A couple other things to try, given that you can provoke the failure
> fairly easily:
> . . .
> 1. In studying the code, it bothers me a bit that P_NEW is the same as
> InvalidBlockNumber.  The intended uses of P_NEW appear to be adequately
> . . .
> 2. I'm also eyeing this bit of code in hio.c:
>
> If someone else has just extended the relation, it's possible that this
> will allow a process to get to the page before the intended extender has
> . . .

We tried all of these suggestions and still get the problem.  Nothing
interesting in the log file so I guess the Asserts did not fire.

We are going to try experimenting with different kernels now.  Unless
anyone has any other suggestions.

__
Marc

pgsql-hackers by date:

Previous
From: "Marko Kreen"
Date:
Subject: [RFC] txid: module for 64-bit external transaction IDs
Next
From: Tom Lane
Date:
Subject: Re: Index corruption