Re: speeding up planning with partitions - Mailing list pgsql-hackers

From Amit Langote
Subject Re: speeding up planning with partitions
Date
Msg-id 753732c0-c329-0e4f-0ce6-93f55a79695c@lab.ntt.co.jp
Whole thread Raw
In response to Re: speeding up planning with partitions  (Justin Pryzby <pryzby@telsasoft.com>)
List pgsql-hackers
On 2019/01/07 23:13, Justin Pryzby wrote:
> The issue was this:
>>> It turns out 1050 open()s are due to historic data which is no longer being
>>> loaded and therefor never converted to relkind=p (but hasn't exceeded the
>>> retention interval so not yet DROPped, either).
> 
> So there's no evidence of any issue with the patch.

Ah, so by this you had meant that the historic data is still a old-style
(9.6-style) inheritance hierarchy, which gets folded under the UNION ALL
whose other children are new-style partitioned tables.

Thanks,
Amit



pgsql-hackers by date:

Previous
From: Stephen Frost
Date:
Subject: Re: Displaying and dumping of table access methods
Next
From: Andres Freund
Date:
Subject: Re: Displaying and dumping of table access methods