| From: | Richard Guo <guofenglinux(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, hackerzheng666(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #19924: unrecognized node type in create_plan_recurse: UNION, LIMIT, json_populate_recordset, inheritance |
| Date: | 2026-11-21 01:15:52 |
| Message-ID: | CAMbWs495pNV3E+hZyjotvUb1iQaU804sg6+2t=XO+y8zbHx9EA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Sat, Nov 21, 2026 at 7:48 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Ah, I identified the problem and a possible fix. The root culprit is
> in grouping_planner():
I haven't had a close look at this bug, but I feel that this is the
same bug as [1], where Jeevan proposed the same parent check. His
reproducer fails on v18 too, so it predates 8300d3ad4.
> What I do suggest is that add_partial_path could check for
> a mismatched Path.parent pointer and cowardly refuse to pfree a
> Path that was originally made for some other parent rel.
+1. I think add_path() should get the same check, as in Jeevan's
patch. create_ordered_paths() passes input_rel's sorted paths to
add_path() unchanged, which breaks the same rule, though it doesn't
crash today.
[1] https://postgr.es/m/CAM2+6=XaYtMGwh27O7oDTfAw7kV4VdUVbxC2RVzWtKz_ysekKw@mail.gmail.com
- Richard
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2026-11-21 02:24:58 | Re: BUG #19924: unrecognized node type in create_plan_recurse: UNION, LIMIT, json_populate_recordset, inheritance |
| Previous Message | Christophe Pettus | 2026-11-21 00:16:37 | Re: BUG #19927: PostgreSQL 16: SQL dump adds experimental/incompatible options like \restrict |