Re: Transaction, Rollback and Database Corruption question,

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Joe Kislo <kislo(at)athenium(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Transaction, Rollback and Database Corruption question,
Date: 2000-11-22 04:58:55
Message-ID: 10416.974869135@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Joe Kislo <kislo(at)athenium(dot)com> writes:
>>>> FATAL 1: my bits moved right off the end of the world!
>>>> Recreate index pg_attribute_relid_attnam_index.
>>
>> We've heard sporadic reports of this, but I've never been able to
>> reproduce it myself. If you can submit a reproducible test script,
>> it'd be a big help.

> Oh.. it's repeatable :) I will upgrade to 7.0.3 tomorrow at work, and
> see if it still happens.. I had been assuming it had something to do
> with the same problem described at the top (so it may be fixed by
> 7.0.3).

Probably it's not fixed. My suspicion is that there's some corner-case
bug lurking in the btree index routines. With a reproducible test case,
we could find and squash it... but I've been over that code with a
flinty eye, and I haven't found it yet.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message rob 2000-11-22 05:49:29 Synchronization Toolkit
Previous Message Patrick Robin 2000-11-22 00:37:34 backend dies when a user defined type returns null