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

Dirk Lutzebäck <lutzeb@aeccom.com>

From: Dirk Lutzebaeck <lutzeb@aeccom.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: hackers@postgreSQL.org
Date: 1999-05-05T07:30:35Z
Lists: pgsql-hackers
Tom Lane writes:
 > Dirk Lutzebaeck <lutzeb@aeccom.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.

Yes, thanks, recreating the index cures the problem.

 > 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.

Does this mean they can deadlock themselves?  Is this also true for
6.4.2? I probably switch back then.

Thanks, Dirk