Re: postgres_fdw: Add more test coverage for EvalPlanQual testing - Mailing list pgsql-hackers

From Etsuro Fujita
Subject Re: postgres_fdw: Add more test coverage for EvalPlanQual testing
Date
Msg-id CAPmGK16ghshhbM4mF1_+O2nUbKTgoJ0XD4+F-eyhep4Gk=J2FA@mail.gmail.com
Whole thread Raw
In response to postgres_fdw: Add more test coverage for EvalPlanQual testing  (Etsuro Fujita <etsuro.fujita@gmail.com>)
List pgsql-hackers
On Sat, Nov 1, 2025 at 8:18 PM Etsuro Fujita <etsuro.fujita@gmail.com> wrote:
> In [1] it was pointed out that there is no test coverage for
> postgresRecheckForeignScan.  So I would like to propose to add test
> cases to cover that function (and related core functions like
> ForeignRecheck), as promised in that thread.  Please find attached a
> patch.  (Note that commit 12609fbac, which fixes an EPQ issue reported
> in [1], added a test case for ExecScanFetch(), but didn't add any test
> cases for that function.)
>
> In the patch I modified all permutations, including existing one, to
> use per-session setup doing "BEGIN ISOLATION LEVEL READ COMMITTED",
> for simplicity, and modified existing step names/comments a little bit
> to match new ones, for consistency.
>
> Like commit 12609fbac, I would also like to propose to back-patch this
> to all supported versions.

There seemed to be no objections, so pushed and back-patched.

Best regards,
Etsuro Fujita



pgsql-hackers by date:

Previous
From: David Rowley
Date:
Subject: Re: Teaching planner to short-circuit empty UNION/EXCEPT/INTERSECT inputs
Next
From: Etsuro Fujita
Date:
Subject: Re: Obsolete comment in ExecScanReScan()