| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Beena Emerson <memissemerson(at)gmail(dot)com> |
| Cc: | David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>, amul sul <sulamul(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Dilip Kumar <dilipbalaut(at)gmail(dot)com> |
| Subject: | Re: [HACKERS] Runtime Partition Pruning |
| Date: | 2017-12-04 02:06:23 |
| Message-ID: | CA+TgmoZJeYwff=aLTkAo0N5jkHCmZHBdFf_wsWuQkj5Yix95qw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Dec 2, 2017 at 3:33 AM, Beena Emerson <memissemerson(at)gmail(dot)com> wrote:
> Append (cost=0.00..395.10 rows=9 width=8) (actual time=0.119..0.119
> rows=0 loops=1) (run-time partition pruning: on)
If we can, it would be better to show something a bit more precise,
like the table being used for run-time pruning, or the expression
being used for pruning.
Also, we shouldn't use an ad-hoc format like "(run-time
partition-pruning: on)"; rather, we should display something using one
of the ExplainPropertyBlah functions in explain.c.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ashutosh Bapat | 2017-12-04 02:14:43 | Re: [HACKERS] Partition-wise aggregation/grouping |
| Previous Message | Ashutosh Bapat | 2017-12-04 02:04:43 | Re: [HACKERS] Partition-wise join for join between (declaratively) partitioned tables |