Re: BUG #15336: Wrong cursor's bacward fetch results in select with ALL(subquery)

From: Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org, v(dot)g(dot)baranoff(at)gmail(dot)com
Subject: Re: BUG #15336: Wrong cursor's bacward fetch results in select with ALL(subquery)
Date: 2018-08-17 15:44:46
Message-ID: 877ekp2e3g.fsf@news-spur.riddles.org.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

>>>>> "Tom" == Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:

>> It turns out to be also necessary to do this in ExecSetParamPlan,
>> though I couldn't find a way to make a stable regression test for
>> that - my manual tests were based on putting a subselect inside a
>> volatile construct like CASE WHEN random() < x THEN.

Tom> Looks sane to me ...

Pushed.

--
Andrew (irc:RhodiumToad)

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2018-08-17 16:49:47 BUG #15338: pg_restore --disable-triggers --data-only AND schema for table is not set.
Previous Message Nandakumar M 2018-08-17 15:40:34 Row exists in a table that violates Foreign key constraint