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 CAPmGK15zAxBOvLjcx9C2pLwdFqUnESg6h300cbvysupcydPmYA@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)  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
On Tue, Jul 16, 2024 at 5:01 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Etsuro Fujita <etsuro.fujita@gmail.com> writes:
> > On Mon, Jul 15, 2024 at 10:55 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> >> Uh ... does this ensure that the data hasn't changed?
>
> > postgres_fdw opens a remote transaction using REPEATABLE READ or
> > SERIALIZABLE, so the recreated cursor uses the same snapshot except
> > changes made by the remote transaction.
>
> Ah, right.

Pushed and back-patched to v15 after adding a comment for the test
case.  Thanks for reviewing!

Best regards,
Etsuro Fujita



pgsql-bugs by date:

Previous
From: Hayden Sim
Date:
Subject: Re: BUG #18544: Setting local config_parameter to DEFAULT behaves unexpectedly when using period in config name
Next
From: PG Bug reporting form
Date:
Subject: BUG #18545: \dt breaks transaction, calling error when executed in SET SESSION AUTHORIZATION