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 877ekp2e3g.fsf@news-spur.riddles.org.uk
Whole thread Raw
In response to Re: BUG #15336: Wrong cursor's bacward fetch results in select with ALL(subquery)  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
>>>>> "Tom" == Tom Lane <tgl@sss.pgh.pa.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)


pgsql-bugs by date:

Previous
From: Nandakumar M
Date:
Subject: Row exists in a table that violates Foreign key constraint
Next
From: PG Bug reporting form
Date:
Subject: BUG #15338: pg_restore --disable-triggers --data-only AND schema fortable is not set.