| From: | Andrey Borodin <x4mmm(at)yandex-team(dot)ru> |
|---|---|
| To: | Amit Khandekar <amitdkhan(dot)pg(at)gmail(dot)com> |
| Cc: | Pavel Borisov <pashkin(dot)elfe(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Speeding up GIST index creation for tsvectors |
| Date: | 2020-12-13 15:58:18 |
| Message-ID: | 047FF29B-95E8-4ABA-878B-2974B5B6A377@yandex-team.ru |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> 13 дек. 2020 г., в 17:46, Amit Khandekar <amitdkhan(dot)pg(at)gmail(dot)com> написал(а):
>
> On Thu, 10 Dec 2020 at 20:43, Pavel Borisov <pashkin(dot)elfe(at)gmail(dot)com> wrote:
>>
>> Hi, Amit!
>> It's really cool to hear about another GiST improvement proposal. I'd like to connect recently committed GiST ordered build discussion here [1] and further improvement proposed [2]
>>
>> I've tested feature [1] and got 2.5-3 times speed improvement which is much better I believe.
>
> Yeah, I am completely new to the GIST stuff, but I had taken a quick
> look at the sortsupport feature for GIST, and found it very
> interesting. I believe it's an additional option for making the gist
> index builds much faster.
+1
This will make all INSERTs and UPDATES for tsvector's GiSTs.
Also I really like idea of taking advantage of hardware capabilities like __builtin_* etc wherever possible.
Meanwhile there are at least 4 incarnation of hemdistsign() functions that are quite similar. I'd propose to refactor them somehow...
Thanks!
Best regards, Andrey Borodin.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-12-13 16:49:31 | HASH_BLOBS hazards (was Re: PATCH: logical_work_mem and logical streaming of large in-progress transactions) |
| Previous Message | Amit Khandekar | 2020-12-13 12:46:54 | Re: Speeding up GIST index creation for tsvectors |