Re: TRAP: failed Assert("outerPlan != NULL") in postgres_fdw.c - Mailing list pgsql-bugs

From Michael Paquier
Subject Re: TRAP: failed Assert("outerPlan != NULL") in postgres_fdw.c
Date
Msg-id aNR7Zi_1-4gtYeI8@paquier.xyz
Whole thread Raw
In response to Re: TRAP: failed Assert("outerPlan != NULL") in postgres_fdw.c  (Masahiko Sawada <sawada.mshk@gmail.com>)
Responses Re: TRAP: failed Assert("outerPlan != NULL") in postgres_fdw.c
List pgsql-bugs
On Wed, Sep 24, 2025 at 09:45:26AM -0700, Masahiko Sawada wrote:
> On Wed, Sep 24, 2025 at 3:28 AM Etsuro Fujita <etsuro.fujita@gmail.com> wrote:
>> I took a quick glance at the patch.  My initial comment is: it only
>> includes the test case discussed here, but I think it's a good idea to
>> add more cases in it (that exercise code paths in
>> postgresRecheckForeignScan), as I mentioned upthread.  What do you
>> think about that?  If no objections, I'd like to update it to include
>> such cases.
>
> +1 to add more test cases for the code paths in postgresRecheckForeignScan.

+1.  Would these be included in the same isolation test?  That may be
cleaner, especially as it seems like the EPQ re-evaluations should be
able to happen with the same schema as the one set up by the test.
--
Michael

Attachment

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #19063: Heavily nesting trivial ROW projections produces out of memory error
Next
From: Lukas Eder
Date:
Subject: Re: BUG #19063: Heavily nesting trivial ROW projections produces out of memory error