aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistbuild.c
diff options
context:
space:
mode:
authorHeikki Linnakangas <heikki.linnakangas@iki.fi>2021-04-07 14:33:21 +0300
committerHeikki Linnakangas <heikki.linnakangas@iki.fi>2021-04-07 14:33:21 +0300
commitd92b1cdbab408d8f1299257125c9ae375f3ca644 (patch)
treee75e26cae720ad2f4a0e1d8ef071ae197924c45a /src/backend/access/gist/gistbuild.c
parent9f984ba6d23dc6eecebf479ab1d3f2e550a4e9be (diff)
downloadpostgresql-d92b1cdbab408d8f1299257125c9ae375f3ca644.tar.gz
postgresql-d92b1cdbab408d8f1299257125c9ae375f3ca644.zip
Revert "Add sortsupport for gist_btree opclasses, for faster index builds."
This reverts commit 9f984ba6d23dc6eecebf479ab1d3f2e550a4e9be. It was making the buildfarm unhappy, apparently setting client_min_messages in a regression test produces different output if log_statement='all'. Another issue is that I now suspect the bit sortsupport function was in fact not correct to call byteacmp(). Revert to investigate both of those issues.
Diffstat (limited to 'src/backend/access/gist/gistbuild.c')
-rw-r--r--src/backend/access/gist/gistbuild.c1
1 files changed, 0 insertions, 1 deletions
diff --git a/src/backend/access/gist/gistbuild.c b/src/backend/access/gist/gistbuild.c
index a90e3de3326..1054f6f1f2e 100644
--- a/src/backend/access/gist/gistbuild.c
+++ b/src/backend/access/gist/gistbuild.c
@@ -260,7 +260,6 @@ gistbuild(Relation heap, Relation index, IndexInfo *indexInfo)
/*
* Sort all data, build the index from bottom up.
*/
- elog(DEBUG1, "using sorted GiST build");
buildstate.sortstate = tuplesort_begin_index_gist(heap,
index,
maintenance_work_mem,