| From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | Robert Haas <rhaas(at)postgresql(dot)org> |
| Cc: | pgsql-committers <pgsql-committers(at)postgresql(dot)org> |
| Subject: | Re: pgsql: Don't scan partitioned tables. |
| Date: | 2017-03-21 14:01:19 |
| Message-ID: | CANP8+jL_tqe+Jr-_tCWyHp+-vvYCO4jnOkRVi0uB_1Nim7uEBQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
On 21 March 2017 at 13:48, Robert Haas <rhaas(at)postgresql(dot)org> wrote:
> Don't scan partitioned tables.
Sounds good.
> Aside from the obvious advantage of avoiding some work at execution
> time, this has two other advantages. First, it may improve the
> planner's decision-making in some cases since the empty relation
> might throw things off.
I was surprised to see that an Append node still exists when there is
only one child plan to be appended. I thought removing that was the
whole point of the patch?
> Second, it paves the way to getting rid of
> the storage for partitioned tables altogether.
I thought we already discussed that. Seems strange to mention
something not very important that might happen in the future. We could
save much more space by optimising FSM.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2017-03-21 14:11:34 | Re: pgsql: Don't scan partitioned tables. |
| Previous Message | Robert Haas | 2017-03-21 13:48:08 | pgsql: Don't scan partitioned tables. |