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

From: Etsuro Fujita <etsuro(dot)fujita(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: eric(dot)cyr(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #17889: Invalid cursor direction for a foreign scan that reached the fetch_size (MOVE BACKWARD ALL IN cX)
Date: 2024-07-15 10:51:03
Message-ID: CAPmGK17-1hPixcv0=t6UYjb5=p9qryr-O0BGoNvcUuGw_pRWtA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Fri, Jul 5, 2024 at 9:49 PM Etsuro Fujita <etsuro(dot)fujita(at)gmail(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Aleksander Alekseev 2024-07-15 11:23:03 Re: BUG #18534: ERROR: portal "C_n" does not exist type of error getting thrown.
Previous Message PG Bug reporting form 2024-07-15 10:00:01 BUG #18541: Reattaching a partition referenced by a foreign key fails with an error