Re: Runtime pruning problem - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Runtime pruning problem
Date
Msg-id 20190912141153.GA31190@alvherre.pgsql
Whole thread Raw
In response to Re: Runtime pruning problem  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Runtime pruning problem
Re: Runtime pruning problem
List pgsql-hackers
On 2019-Jul-30, Tom Lane wrote:

> I wrote:
> > This may be arguing for a change in ruleutils' existing behavior,
> > not sure.  But when dealing with traditional-style inheritance,
> > I've always thought that Vars above the Append were referring to
> > the parent rel in its capacity as the parent, not in its capacity
> > as the first child.  With new-style partitioning drawing a clear
> > distinction between the parent and all its children, it's easier
> > to understand the difference.
> 
> OK, so experimenting, I see that it is a change: [...]

> The portion of this below the Append is fine, but I argue that
> the Vars above the Append should say "part", not "part_p1".
> In that way they'd look the same regardless of which partitions
> have been pruned or not.

So is anyone working on a patch to use this approach?

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Misleading comment in tuplesort_set_bound
Next
From: Tom Lane
Date:
Subject: Re: Runtime pruning problem