Re: [HACKERS] major flaw in 6.5beta1??? (UPDATE/INSERT waiting)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Dirk Lutzebaeck <lutzeb(at)aeccom(dot)com>
Cc: hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] major flaw in 6.5beta1??? (UPDATE/INSERT waiting)
Date: 1999-05-04 16:20:29
Message-ID: 368.925834829@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Dirk Lutzebaeck <lutzeb(at)aeccom(dot)com> writes:
> cs=> select envelope from recipient where envelope=510349;
> [ returns a tuple that obviously fails the WHERE condition ]

Yipes. Do you have an index on the envelope field, and if so is
it being used for this query? (Use EXPLAIN to check.) My guess
is that the index is corrupted. Dropping and recreating the index
would probably set things right.

Of course the real issue is how it got corrupted. Hiroshi found
an important bug in btree a few days ago, and there is a discussion
going on right now about lock-manager bugs that might possibly allow
multiple backends to corrupt data that they're concurrently updating.
But I have no idea if either of those explains your problem.

regards, tom lane

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 1999-05-04 16:55:03 Re: [HACKERS] varchar-array.patch applied
Previous Message Tom Lane 1999-05-04 16:07:55 Advice wanted on backend memory management