Re: postgres_fdw: Provide better emulation of READ COMMITTED behavior - Mailing list pgsql-hackers

From Robert Haas
Subject Re: postgres_fdw: Provide better emulation of READ COMMITTED behavior
Date
Msg-id CA+TgmoaYs6DLXrZB8NWzUi3YPL9yvBhFOG4UMENMCJ+WY2pn5A@mail.gmail.com
Whole thread Raw
Responses Re: postgres_fdw: Provide better emulation of READ COMMITTED behavior
List pgsql-hackers
On Thu, Dec 5, 2024 at 4:41 AM Etsuro Fujita <etsuro.fujita@gmail.com> wrote:
> Comments welcome!  Maybe I am missing something, though.

I have a hard time seeing how this would work if cursors are in use on
the main server. Say I do this:

DECLARE foo CURSOR FOR SELECT * FROM ft1 UNION ALL SELECT * FROM ft2;
...fetch some rows from cursor foo but few enough that we only scan ft1...
...do something that causes a snapshot refresh like issue another query...
...fetch more rows from cursor foo until we start scanning ft2...

--
Robert Haas
EDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Potential null pointer dereference in postgres.c
Next
From: Peter Eisentraut
Date:
Subject: Re: meson missing test dependencies