Re: BUG #2166: attempted to update invisible tuple

From: Jaime Casanova <systemguards(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Euler Taveira de Oliveira <eulerto(at)yahoo(dot)com(dot)br>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #2166: attempted to update invisible tuple
Date: 2006-01-12 17:37:43
Message-ID: c2d9e70e0601120937p23c5aba1j69a26366f6cbc560@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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 ;)

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2006-01-12 19:28:26 Re: BUG #2162: Same as bug #1679 - finite() - unresolved symbol
Previous Message Tom Lane 2006-01-12 17:14:54 Re: BUG #2166: attempted to update invisible tuple