| From: | Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp> |
|---|---|
| To: | hosoya(dot)yuzuko(at)lab(dot)ntt(dot)co(dot)jp |
| Cc: | thibaut(dot)madelaine(at)dalibo(dot)com, imai(dot)yoshikazu(at)jp(dot)fujitsu(dot)com, Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Problem with default partition pruning |
| Date: | 2019-03-19 02:40:41 |
| Message-ID: | 20190319.114041.61514593.horiguchi.kyotaro@lab.ntt.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hello.
At Fri, 15 Mar 2019 17:30:07 +0900 (Tokyo Standard Time), Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp> wrote in <20190315(dot)173007(dot)147577546(dot)horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>
> The patch relies on the fact(?) that the lowest index is always
> -1 in range partition and uses it as pseudo default
> partition. I'm not sure it is really the fact and anyway it
> donsn't seem the right thing to do. Could you explain how it
> works, not what you did in this patch?
I understood how it works but still uneasy that only list
partitioning requires scan_default. Anyway please ignore this.
regards.
--
Kyotaro Horiguchi
NTT Open Source Software Center
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Yamaji, Ryo | 2019-03-19 02:56:38 | RE: [HACKERS] Cached plans and statement generalization |
| Previous Message | Eric Hanson | 2019-03-19 02:38:19 | extensions are hitting the ceiling |