| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>, Robert Haas <robertmhaas(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: no partition pruning when partitioning using array type |
| Date: | 2018-07-09 20:53:14 |
| Message-ID: | 4384.1531169594@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
> The same occurs in 11 and master. I think this is because the
> polymorphic type is resolved for the function ahead of time (at
> table creation time); partexprs shows
> ({FUNCEXPR :funcid 35757 :funcresulttype 23 :funcretset false :funcvariadic false :funcformat 0 :funccollid 0 :inputcollid 0 :args ({VAR :varno 1 :varattno 1 :vartype 23 :vartypmod -1 :varcollid 0 :varlevelsup 0 :varnoold 1 :varoattno 1 :location 46}) :location 44})
> where the ":funcresulttype 23" bit indicates that the function is
> returning type integer, which I find a bit odd. I think if we were to
> leave it as funcresulttype anynonarray, pruning would work.
... at the cost of breaking many other things.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-07-09 21:25:50 | Re: peripatus build failures.... |
| Previous Message | Andres Freund | 2018-07-09 20:39:15 | Re: pgsql: Fix crash when ALTER TABLE recreates indexes on partitions |