pg.ddx.io  pgsql-committers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Alexander Korotkov <akorotkov@postgresql.org>
To: pgsql-committers@lists.postgresql.org
Subject: pgsql: Reduce non-leaf keys overlap in GiST indexes produced by a sorte
Date: Mon, 07 Feb 2022 20:21:16 +0000
Message-ID: <E1nHAVg-0006y9-U5@gemulon.postgresql.org> (raw)

Reduce non-leaf keys overlap in GiST indexes produced by a sorted build

The GiST sorted build currently chooses split points according to the only page
space utilization.  That may lead to higher non-leaf keys overlap and, in turn,
slower search query answers.

This commit makes the sorted build use the opclass's picksplit method.  Once
four pages at the level are accumulated, the picksplit method is applied until
each split partition fits the page.  Some of our split algorithms could show
significant performance degradation while processing 4-times more data at once.
But those opclasses haven't received the sorted build support and shouldn't
receive it before their split algorithms are improved.

Discussion: https://postgr.es/m/CAHqSB9jqtS94e9%3D0vxqQX5dxQA89N95UKyz-%3DA7Y%2B_YJt%2BVW5A%40mail.gmail.com
Author: Aliaksandr Kalenik, Sergei Shoulbakov, Andrey Borodin
Reviewed-by: Björn Harrtell, Darafei Praliaskouski, Andres Freund
Reviewed-by: Alexander Korotkov

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/f1ea98a7975e15cefdb446385880a2f55224ee7d

Modified Files
--------------
contrib/pageinspect/expected/gist.out |  18 +--
src/backend/access/gist/README        |  16 ++
src/backend/access/gist/gistbuild.c   | 271 +++++++++++++++++++++-------------
src/tools/pgindent/typedefs.list      |   2 +-
4 files changed, 197 insertions(+), 110 deletions(-)



Message-ID: <E1nHAVg-0006y9-U5@gemulon.postgresql.org>
Permalink:  ../E1nHAVg-0006y9-U5@gemulon.postgresql.org/
Also on:    postgresql.org/message-id/E1nHAVg-0006y9-U5@gemulon.postgresql.org

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-committers@postgresql.org
  Cc: akorotkov@postgresql.org
  Subject: Re: pgsql: Reduce non-leaf keys overlap in GiST indexes produced by a sorte
  In-Reply-To: <E1nHAVg-0006y9-U5@gemulon.postgresql.org>
  References: <E1nHAVg-0006y9-U5@gemulon.postgresql.org>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox