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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Etsuro Fujita <etsuro(dot)fujita(at)gmail(dot)com>
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 13:55:28
Message-ID: 3147482.1721051728@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Etsuro Fujita <etsuro(dot)fujita(at)gmail(dot)com> writes:
> 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?

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

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Aleksander Alekseev 2024-07-15 14:04:19 Re: libpq: unexpected return code from PQexecParams with a DO INSTEAD rule present
Previous Message Tender Wang 2024-07-15 13:18:34 Re: BUG #18541: Reattaching a partition referenced by a foreign key fails with an error