Re: Assert failure in try_nestloop_path()

From: Alexander Lakhin <exclusion(at)gmail(dot)com>
To: Richard Guo <guofenglinux(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Tender Wang <tndrwang(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Assert failure in try_nestloop_path()
Date: 2026-09-26 17:00:00
Message-ID: 4a0d7906-14f4-4992-8815-16e17e1f6655@gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hello Richard and Tom,

10.09.2026 04:36, Richard Guo wrote:
> On Wed, Sep 9, 2026 at 11:35 PM Tom Lane<tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
>> I wonder if we should leave the Assert bits out of v19. The intent to
>> have hard prevention of duplicate clauses is a brand new aspiration,
>> and I have pretty much no faith that no such cases remain. I don't
>> really want to commit to fixing all such cases in v19.
> Fair point. I kept the assertions on HEAD only, with a note in the
> commit message.
>
> I've pushed both to master and v19.

I've discovered that:
echo "geqo_threshold = 2" >/tmp/temp.config
TEMP_CONFIG=/tmp/temp.config TESTS="partition_join" make -s check-tests

triggers one of the assertions:
TRAP: failed Assert("no_duplicate_clause_serials(*restrict_clauses)"), File: "relnode.c", Line: 2079, PID: 634394

Could you have a look, please?

Best regards,
Alexander

In response to

Browse pgsql-hackers by date

  From Date Subject
Previous Message Jelte Fennema-Nio 2026-09-26 16:16:41 Re: Extension security improvement: Add support for extensions with an owned schema