Re: Internal error XX000 with enable_partition_pruning=on, pg 11 beta1 on Debian
| От | Tom Lane |
|---|---|
| Тема | Re: Internal error XX000 with enable_partition_pruning=on, pg 11 beta1 on Debian |
| Дата | |
| Msg-id | 14685.1533683389@sss.pgh.pa.us обсуждение исходный текст |
| Ответ на | Re: Internal error XX000 with enable_partition_pruning=on, pg 11beta1 on Debian (Rushabh Lathia <rushabh.lathia@gmail.com>) |
| Ответы |
Re: Internal error XX000 with enable_partition_pruning=on, pg 11beta1 on Debian
|
| Список | pgsql-hackers |
Rushabh Lathia <rushabh.lathia@gmail.com> writes:
> Consider the below case:
I initially thought the rule might be messing stuff up, but you can get
the same result without the rule by writing out the transformed query
by hand:
regression=# explain UPDATE pt_p1 SET a = 3 from pt
WHERE pt.a = 2 and pt.a = pt_p1.a;
ERROR: child rel 2 not found in append_rel_array
With enable_partition_pruning=off this goes through without an error.
I suspect the join pruning stuff is getting confused by the overlap
between the two partitioning trees involved in the join; although the
fact that one of them is the target rel must be related too, because
if you just write a SELECT for this join it's fine.
I rather doubt that this case worked before 1b54e91fa ... no time
to look closer today, though.
regards, tom lane
В списке pgsql-hackers по дате отправления: