| From: | Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org, v(dot)g(dot)baranoff(at)gmail(dot)com, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: BUG #15336: Wrong cursor's bacward fetch results in select with ALL(subquery) |
| Date: | 2018-08-17 14:38:41 |
| Message-ID: | 87efex2hd2.fsf@news-spur.riddles.org.uk |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
>>>>> "Alvaro" == Alvaro Herrera <alvherre(at)2ndquadrant(dot)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)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-08-17 14:53:11 | Re: BUG #15333: pg_dump error on large table -- "pg_dump: could not stat file...Unknown error" |
| Previous Message | Bruce Momjian | 2018-08-17 14:27:59 | Re: [PG_UPGRADE] 9.6 to 10.5 |