diff options
| author | Heikki Linnakangas <heikki.linnakangas@iki.fi> | 2025-04-03 13:46:35 +0300 |
|---|---|---|
| committer | Heikki Linnakangas <heikki.linnakangas@iki.fi> | 2025-04-03 13:46:35 +0300 |
| commit | e4309f73f698851a2f7d49ca5e98e3e188400891 (patch) | |
| tree | 7ebe9c998f9778f246baacb5776d98bba968313f /doc/src/sgml/btree-gist.sgml | |
| parent | 9370978da8ac8f0e31867859282b0f2be724fe48 (diff) | |
| download | postgresql-e4309f73f698851a2f7d49ca5e98e3e188400891.tar.gz postgresql-e4309f73f698851a2f7d49ca5e98e3e188400891.zip | |
Add support for sorted gist index builds to btree_gist
This enables sortsupport in the btree_gist extension for faster builds
of gist indexes.
Sorted gist index build strategy is the new default now. Regression
tests are unchanged (except for one small change in the 'enum' test to
add coverage for enum values added later) and are using the sorted
build strategy instead.
One version of this was committed a long time ago already, in commit
9f984ba6d2, but it was quickly reverted because of buildfarm
failures. The failures were presumably caused by some small bugs, but
we never got around to debug and commit it again. This patch was
written from scratch, implementing the same idea, with some fragments
and ideas from the original patch.
Author: Bernd Helmle <mailings@oopsware.de>
Author: Andrey Borodin <x4mmm@yandex-team.ru>
Discussion: https://www.postgresql.org/message-id/64d324ce2a6d535d3f0f3baeeea7b25beff82ce4.camel@oopsware.de
Diffstat (limited to 'doc/src/sgml/btree-gist.sgml')
| -rw-r--r-- | doc/src/sgml/btree-gist.sgml | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/doc/src/sgml/btree-gist.sgml b/doc/src/sgml/btree-gist.sgml index 31e7c78aaef..a4c1b99be1f 100644 --- a/doc/src/sgml/btree-gist.sgml +++ b/doc/src/sgml/btree-gist.sgml @@ -53,6 +53,13 @@ </para> <para> + By default <filename>btree_gist</filename> builds <acronym>GiST</acronym> index with + <function>sortsupport</function> in <firstterm>sorted</firstterm> mode. This usually results in + much faster index built speed. It is still possible to revert to buffered built strategy + by using the <literal>buffering</literal> parameter when creating the index. + </para> + + <para> This module is considered <quote>trusted</quote>, that is, it can be installed by non-superusers who have <literal>CREATE</literal> privilege on the current database. |