Re: open/lseek overhead with many partitions (including with "fasterpartitioning pruning") - Mailing list pgsql-hackers

From David Rowley
Subject Re: open/lseek overhead with many partitions (including with "fasterpartitioning pruning")
Date
Msg-id CAKJS1f8DjC+iWH4CCeChN0=cS8=U+t9JBnVoH6sz=dVhnUbRYw@mail.gmail.com
Whole thread Raw
In response to open/lseek overhead with many partitions (including with "fasterpartitioning pruning")  (Justin Pryzby <pryzby@telsasoft.com>)
Responses Re: open/lseek overhead with many partitions (including with "fasterpartitioning pruning")  (Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>)
List pgsql-hackers
On 4 April 2018 at 07:46, Justin Pryzby <pryzby@telsasoft.com> wrote:
> TLDR: even with "faster pruning" patch, pg11dev open()+lseek() every file
> backing every table being queried, even for those partitions eventually
> "excluded".

Yeah, this will no doubt be due to the fact that we still build
RelOptInfos in the planner for all partitions, so we're still doing
get_relation_info() and estimate_rel_size() for each of those. It
might be possible to delay that call until we know we're going to need
the partition.  I imagine we wouldn't need to know the size of the
relation until after set_rel_sizes, but I've not checked.


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


pgsql-hackers by date:

Previous
From: Amit Langote
Date:
Subject: Re: open/lseek overhead with many partitions (including with "fasterpartitioning pruning")
Next
From: Amit Langote
Date:
Subject: Re: open/lseek overhead with many partitions (including with "fasterpartitioning pruning")