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 Etsuro Fujita
Subject Re: BUG #17889: Invalid cursor direction for a foreign scan that reached the fetch_size (MOVE BACKWARD ALL IN cX)
Date
Msg-id CAPmGK17-1hPixcv0=t6UYjb5=p9qryr-O0BGoNvcUuGw_pRWtA@mail.gmail.com
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
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?  If we had a way to check the
> scrollability of a remote cursor created without the SCROLL option, we
> could avoid doing so for scrollable cursors, but we do not have it, so
> I modified it to recreate it in any case.

Barring objections, I will push this and back-patch to v15.

Best regards,
Etsuro Fujita



pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #18541: Reattaching a partition referenced by a foreign key fails with an error
Next
From: Aleksander Alekseev
Date:
Subject: Re: BUG #18534: ERROR: portal "C_n" does not exist type of error getting thrown.