On 21 March 2017 at 13:48, Robert Haas <[email protected]> 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 -- Sent via pgsql-committers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
