Postgres Pro
Downloads
Home   >   mailing lists

Re: Should total_pages be calculated after partition pruning andconstraint exclusion? - Mailing list pgsql-hackers

From David Rowley
Subject Re: Should total_pages be calculated after partition pruning andconstraint exclusion?
Date
Msg-id CAKJS1f-YHrAfM0+PBbQvFMRUWzHZirQbMtg07rVHu-JYLtTdOQ@mail.gmail.com
Whole thread Raw
In response to Re: Should total_pages be calculated after partition pruning and constraint exclusion?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Should total_pages be calculated after partition pruning and constraint exclusion?
List pgsql-hackers
Tree view 
On 16 May 2018 at 08:10, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> David Rowley <david.rowley@2ndquadrant.com> writes:
>> The attached patch implements the change.
>
> Please add to next CF.  It's a bit late to be doing such things in v11,
> IMO.

If I do that, it'll go under bug fix. It seems strange to delay fixing
this until v12. We've still got 1 week before beta.

-- 
 David Rowley                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [BUGFIX] amcanbackward is not checked before building backward index paths
Next
From: Tom Lane
Date:
Subject: Re: Should total_pages be calculated after partition pruning and constraint exclusion?