Re: Assert failure in try_nestloop_path()

From: Richard Guo <guofenglinux(at)gmail(dot)com>
To: 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-07 03:03:45
Message-ID: CAMbWs4_zg5nV73EgSFj5DTAYqYjNuSyy_FmTG0mDzBuyionyHw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Sep 4, 2026 at 10:50 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Yup, clearly an oversight. Your fix LGTM. I'm not sure that we
> should push it into stable branches: it might destabilize queries that
> people are happy with, and we don't have field complaints about it.
> But v19 should still be fair game at this point.

Thanks for reviewing! I agree that back-patching into stable
branches isn't worth the risk of plan changes, given the lack of field
complaints. I've pushed this to master and v19.

- Richard

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message shihao zhong 2026-09-07 03:07:12 Re: [(known) BUG] DELETE/UPDATE more than one row in partitioned foreign table
Previous Message David Rowley 2026-09-07 03:01:50 Re: SUM(int2)/SUM(int4) do not detect overflow of the int8 accumulator