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: pgsql-bugs(at)lists(dot)postgresql(dot)org
Cc: 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 11:49:19
Message-ID: 87mutl2pv1.fsf@news-spur.riddles.org.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

>>>>> "Andrew" == Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> writes:

Andrew> I'm really not sure yet what the correct fix is, though.

I'm guessing that locally saving/restoring the scan direction in
ExecSubPlan is going to be the best option; it seems to fix the problem,
I'll post a patch in a bit.

--
Andrew (irc:RhodiumToad)

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Amit Langote 2018-08-17 13:18:33 Re: BUG #15334: Partition elimination not working as expected when using enum as partition key
Previous Message PG Bug reporting form 2018-08-17 11:47:11 BUG #15337: partition modify bug? cann't sync relcache in the same session immediate?