Re: BUG #17889: Invalid cursor direction for a foreign scan that reached the fetch_size (MOVE BACKWARD ALL IN cX) - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #17889: Invalid cursor direction for a foreign scan that reached the fetch_size (MOVE BACKWARD ALL IN cX)
Date
Msg-id 3147482.1721051728@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #17889: Invalid cursor direction for a foreign scan that reached the fetch_size (MOVE BACKWARD ALL IN cX)  (Etsuro Fujita <etsuro.fujita@gmail.com>)
Responses Re: BUG #17889: Invalid cursor direction for a foreign scan that reached the fetch_size (MOVE BACKWARD ALL IN cX)
List pgsql-bugs
Etsuro Fujita <etsuro.fujita@gmail.com> writes:
> On Fri, Jul 5, 2024 at 9:49 PM Etsuro Fujita <etsuro.fujita@gmail.com> wrote:
>> To fix, how about instead modifying postgres_fdw so that if the remote
>> server is v15 or later, it just recreates a cursor when rewinding it
>> is needed, like the attached?

Uh ... does this ensure that the data hasn't changed?

            regards, tom lane



pgsql-bugs by date:

Previous
From: Tender Wang
Date:
Subject: Re: BUG #18541: Reattaching a partition referenced by a foreign key fails with an error
Next
From: Aleksander Alekseev
Date:
Subject: Re: libpq: unexpected return code from PQexecParams with a DO INSTEAD rule present