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

From Justin Pryzby
Subject Re: speeding up planning with partitions
Date
Msg-id 20190107141332.GT25379@telsasoft.com
Whole thread Raw
In response to Re: speeding up planning with partitions  (David Rowley <david.rowley@2ndquadrant.com>)
Responses Re: speeding up planning with partitions  (Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>)
List pgsql-hackers
On Mon, Jan 07, 2019 at 09:40:50PM +1300, David Rowley wrote:
> On Fri, 4 Jan 2019 at 04:39, Justin Pryzby <pryzby@telsasoft.com> wrote:
> > Running 11dev with your v10 patch applied, this takes 2244ms with empty buffer
> > cache after postmaster restarted on a totally untuned instance (and a new
> > backend, with no cached opened files).
> >
> > I was curious why it took even 2sec, and why it did so many opens() (but not
> > 20k of them that PG11 does):
> 
> It would be pretty hard to know that without seeing the query plan.

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.

Justin


pgsql-hackers by date:

Previous
From: Jesper Pedersen
Date:
Subject: Re: pg_upgrade: Pass -j down to vacuumdb
Next
From: Masahiko Sawada
Date:
Subject: Re: Using logical replication with older version subscribers