Message-ID: <cea2d8b99e6a6d574ad6a00d059f09b2a72f2624.camel@j-davis.com>
Subject: Re: Skip adding row-marks for non target tables when result
 relation is foreign table.
From: Jeff Davis <pgsql@j-davis.com>
To: Etsuro Fujita <etsuro.fujita@gmail.com>
Cc: SAIKIRAN AVULA <avulasaikiranreddy@gmail.com>, 
	pgsql-hackers@postgresql.org
Date: Wed, 14 Aug 2024 17:56:46 -0700
In-Reply-To: <CAPmGK16H_iHhuwOe_LV4Q2eDnToaU_fFfb21ttB1fS9zBWvLig@mail.gmail.com>
References: 
	<CABg8Gm5z53jv7+2-=RXZ0XYOna7Ts_Yc+TP83qbBU4YDtbAouA@mail.gmail.com>
	 <b8dbfbb9bc98e76f1424f6c64e79e122b88fc09d.camel@j-davis.com>
	 <CAPmGK16H_iHhuwOe_LV4Q2eDnToaU_fFfb21ttB1fS9zBWvLig@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.44.4-0ubuntu2 
MIME-Version: 1.0
Archived-At: <https://www.postgresql.org/message-id/cea2d8b99e6a6d574ad6a00d059f09b2a72f2624.camel%40j-davis.com>
Precedence: bulk

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 that implements late locking for a FDW? I'm
not quite clear on how it's supposed to work.

Regards,
	Jeff Davis