Re: Small performance tweak to run-time partition pruning

From: David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>
To: "Imai, Yoshikazu" <imai(dot)yoshikazu(at)jp(dot)fujitsu(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Small performance tweak to run-time partition pruning
Date: 2018-10-22 20:31:19
Message-ID: CAKJS1f-are-d8SV62jViKFgbwKcALz=tzag0mk_Q3RhS2yCwSg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 18 October 2018 at 16:13, Imai, Yoshikazu
<imai(dot)yoshikazu(at)jp(dot)fujitsu(dot)com> wrote:
> The patch improves the performance about 1.3% which is less than David's
> result, but it seems still improves the performance.

Thanks for doing these benchmarks.

The speedup is small, but it becomes much more significant once other
bottlenecks are removed. More partitions may show a larger increase,
but more partitions also means that a larger range table array gets
built during ExecInitRangeTable(), which is also slow.

--
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 Alvaro Herrera 2018-10-22 22:15:38 Re: pgsql: Avoid duplicate XIDs at recovery when building initial snapshot
Previous Message Heikki Linnakangas 2018-10-22 19:53:36 Re: [PATCH] XLogReadRecord returns pointer to currently read page