From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Richard Guo <guofenglinux(at)gmail(dot)com> |
Cc: | Daniel Gustafsson <daniel(at)yesql(dot)se>, xinwen(at)stu(dot)scu(dot)edu(dot)cn, pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #17700: An assert failed in prepjointree.c |
Date: | 2022-11-29 02:24:13 |
Message-ID: | 793071.1669688653@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Richard Guo <guofenglinux(at)gmail(dot)com> writes:
> BTW, for the test case
> +explain (verbose, costs off)
> +with ctetable as not materialized ( select 1 as f1 )
> +select * from ctetable c1
> +where f1 in ( select c3.f1 from ctetable c2 full join ctetable c3 on true
> );
> Actually we just need to keep 'c3' in a join's nullable side to have the
> PHV created. So we don't have to use full join in the subquery. A left
> join would do.
Actually, the planner reduces the full join to left join anyway;
if it did not, it wouldn't be able to reach the code in question.
I think this formulation is fine because it tests that step along
with the bug proper.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | PG Bug reporting form | 2022-11-29 02:45:48 | BUG #17702: An assert failed in parse_utilcmd.c |
Previous Message | Richard Guo | 2022-11-29 02:19:00 | Re: BUG #17700: An assert failed in prepjointree.c |