Re: BUG #15336: Wrong cursor's bacward fetch results in select with ALL(subquery) - Mailing list pgsql-bugs

From Andrew Gierth
Subject Re: BUG #15336: Wrong cursor's bacward fetch results in select with ALL(subquery)
Date
Msg-id 87efex2hd2.fsf@news-spur.riddles.org.uk
Whole thread Raw
In response to Re: BUG #15336: Wrong cursor's bacward fetch results in select withALL(subquery)  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-bugs
>>>>> "Alvaro" == Alvaro Herrera <alvherre@2ndquadrant.com> writes:

 >> I wonder if we have a contender here for the oldest reported bug in
 >> PG history; while I haven't tested anything older than 9.5, the
 >> incorrect logic seems to date back to the introduction of subqueries
 >> in 6.something.

 Alvaro> Hmm ..

 Alvaro> 8.2 seems fine:

Hah. You're right; the bug is only 10 years old, not 20. It was
apparently introduced in 8.3 by commit c7ff7663e; before that, SubPlans
had a separate EState from the parent plan, so they didn't share the
parent plan's direction indicator.

-- 
Andrew (irc:RhodiumToad)


pgsql-bugs by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [PG_UPGRADE] 9.6 to 10.5
Next
From: Tom Lane
Date:
Subject: Re: BUG #15333: pg_dump error on large table -- "pg_dump: could not stat file...iso-8859-1 error"