Re: Should total_pages be calculated after partition pruning and constraint exclusion?

From: David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Should total_pages be calculated after partition pruning and constraint exclusion?
Date: 2018-05-15 22:51:20
Message-ID: CAKJS1f-YHrAfM0+PBbQvFMRUWzHZirQbMtg07rVHu-JYLtTdOQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 16 May 2018 at 08:10, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> David Rowley <david(dot)rowley(at)2ndquadrant(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2018-05-15 23:04:14 Re: Should total_pages be calculated after partition pruning and constraint exclusion?
Previous Message Tom Lane 2018-05-15 22:41:16 Re: [BUGFIX] amcanbackward is not checked before building backward index paths