| 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-08 13:47:21 |
| Message-ID: | CAMbWs494J+6bcsetBuQPcQa03qceprPO2Y0veCFtZpnv-nPJjw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Sep 8, 2026 at 12:13 PM Richard Guo <guofenglinux(at)gmail(dot)com> wrote:
> Hmm, I don't think bizarre join orderings are required. The duplicate
> arises whenever the qual pushed down into the parameterized path is
> not affected by the commuting outer join, which seems quite a common
> case. Here is an example where the duplicate shows up in the selected
> plan, with the joins performed just in syntactic order:
... and here is a patch to fix it.
Now we have three patches fixing three duplicate-clause issues.
- Richard
| Attachment | Content-Type | Size |
|---|---|---|
| v1-0001-Fix-duplicate-enforcement-of-identical-clone-clau.patch | application/octet-stream | 13.5 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2026-09-08 13:48:21 | Re: docs: Fixes for August 2026 minor release notes (v14-v17) |
| Previous Message | Peter Eisentraut | 2026-09-08 13:44:39 | Re: EXPLAIN ... FOR PORTION OF should not evaluate bounds |