| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> |
| Cc: | Etsuro Fujita <etsuro(dot)fujita(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>, kristianlejao(at)gmail(dot)com |
| Subject: | Re: TRAP: failed Assert("outerPlan != NULL") in postgres_fdw.c |
| Date: | 2025-09-24 23:14:46 |
| Message-ID: | aNR7Zi_1-4gtYeI8@paquier.xyz |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(dot)fujita(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Lukas Eder | 2025-09-25 08:30:34 | Re: BUG #19063: Heavily nesting trivial ROW projections produces out of memory error |
| Previous Message | Tom Lane | 2025-09-24 18:43:29 | Re: BUG #19063: Heavily nesting trivial ROW projections produces out of memory error |