From: | Dirk Lutzebaeck <lutzeb(at)aeccom(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] major flaw in 6.5beta1??? (UPDATE/INSERT waiting) |
Date: | 1999-05-05 07:30:35 |
Message-ID: | 14127.62209.895627.254567@blanc.aeccom.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane writes:
> 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.
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
From | Date | Subject | |
---|---|---|---|
Next Message | Dirk Lutzebaeck | 1999-05-05 07:54:26 | Re: [HACKERS] major flaw in 6.5beta1??? (UPDATE/INSERT waiting) |
Previous Message | Thomas Lockhart | 1999-05-05 06:38:27 | Re: [HACKERS] pg_dump bug (was Re: [SQL] Slow Inserts Again) |