Re: BUG #2166: attempted to update invisible tuple - Mailing list pgsql-bugs

From Jaime Casanova
Subject Re: BUG #2166: attempted to update invisible tuple
Date
Msg-id c2d9e70e0601120937p23c5aba1j69a26366f6cbc560@mail.gmail.com
Whole thread Raw
In response to Re: BUG #2166: attempted to update invisible tuple  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
>
> I think EvalPlanQual is deciding that updated tuples are valid in
> some cases where it shouldn't.  Unfortunately, if that's correct it
> means that all the branches are broken since last August :-(
>
>                        regards, tom lane
>

i reproduced it in 8.1.1, so i guess you are right in tell that old
branches are broken...

--
regards,
Jaime Casanova
(DBA: DataBase Aniquilator ;)

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #2166: attempted to update invisible tuple
Next
From: Tom Lane
Date:
Subject: Re: BUG #2162: Same as bug #1679 - finite() - unresolved symbol