On Thu, Aug 15, 2024 at 9:56 AM Jeff Davis wrote:
> Is there any sample code that implements late locking for a FDW? I'm
> not quite clear on how it's supposed to work.
See the patch in [1]. It would not apply to HEAD anymore, though.
Best regards,
Etsuro Fujita
[1] https://www.postgresql.org/
On Fri, 2024-08-09 at 17:35 +0900, Etsuro Fujita wrote:
> I might be missing something, but I think the extra round trip
> happens
> for each foreign row locked using the RefetchForeignRow() API in
> ExecLockRows(), so I think the overhead is caused in the normal case.
Is there any sample code tha
On Wed, May 22, 2024 at 10:13 AM Jeff Davis wrote:
> On Mon, 2024-05-06 at 23:10 +0100, SAIKIRAN AVULA wrote:
> > Additionally, the commit afb9249d06f47d7a6d4a89fea0c3625fe43c5a5d,
> > which introduced late locking for foreign tables, mentions that the
> > benefits of late locking against a remot
On Mon, 2024-05-06 at 23:10 +0100, SAIKIRAN AVULA wrote:
> I would like to bring to your attention an observation regarding the
> planner's behavior for foreign table update/delete operations. It
> appears that the planner adds rowmarks (ROW_MARK_COPY) for non-target
> tables, which I believe is un
