Re: TRAP: failed Assert("outerPlan != NULL") in postgres_fdw.c

From: Etsuro Fujita <etsuro(dot)fujita(at)gmail(dot)com>
To: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, 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 10:28:02
Message-ID: CAPmGK14sTPK4bz9ii_wQ2L6Z+i+zdjPBE7rMHrbiL6uGQdWL=g@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, Sep 24, 2025 at 6:42 AM Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> wrote:
> I changed the regression tests and used the fix proposed by
> Fujita-san. Please review the attached new version patch.

Thanks for updating the patch!

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.

Anyway I'll review it in more detail.

Best regards,
Etsuro Fujita

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message David Rowley 2025-09-24 10:47:02 Re: The issue of incorrect width estimation in UNION queries
Previous Message Amit Kapila 2025-09-24 08:34:12 Re: Lock timeouts and unusual spikes in replication lag with logical parallel transaction streaming