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

From: Etsuro Fujita <etsuro(dot)fujita(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Masahiko Sawada <sawada(dot)mshk(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-10-07 10:59:14
Message-ID: CAPmGK17wGLtABK20dPzbVORaRKve0_99Zg9bMcLcE+PeE1e6zw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Mon, Oct 6, 2025 at 12:37 PM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
> On Mon, Oct 06, 2025 at 02:15:25AM +0900, Etsuro Fujita wrote:
> > The isolation test fails. I think you failed to update the expected
> > file. Also, you left the useless alias for table a alone...
>
> Yep, the EXPLAIN plan was missing. Another thing that you have missed
> is to update postgres_fdw's .gitignore so as it discards /output_iso/.
>
> The updated patch attached, labelled v6, addresses all that.

LGTM. Thanks for updating the patch including the .gitignore file!

Sawada-san, the patch uses the fix for ExecScanFetch that I proposed,
so if you wouldn't mind, I'd like to take care of this.

Best regards,
Etsuro Fujita

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Masahiko Sawada 2025-10-07 17:25:29 Re: TRAP: failed Assert("outerPlan != NULL") in postgres_fdw.c
Previous Message Marco Boeringa 2025-10-07 09:50:08 Re: Potential "AIO / io workers" inter-worker locking issue in PG18?