Re: [PATCH] Improve amcheck to also check UNIQUE constraint in btree index.

Поиск
Список
Период
Сортировка
Искать
От
Noah Misch
Тема
Re: [PATCH] Improve amcheck to also check UNIQUE constraint in btree index.
Дата
в 02:24:12
Msg-id
20240501022412.85@rfd.leadboat.com
Ответ на
Re: [PATCH] Improve amcheck to also check UNIQUE constraint in btree index. (Pavel Borisov)
Список
Дерево обсуждения
[PATCH] Improve amcheck to also check UNIQUE constraint in btree index. Pavel Borisov <pashkin.elfe@gmail.com>
Re: [PATCH] Improve amcheck to also check UNIQUE constraint in btree index. Pavel Borisov <pashkin.elfe@gmail.com>
Re: [PATCH] Improve amcheck to also check UNIQUE constraint in btree index. Mark Dilger <mark.dilger@enterprisedb.com>
Re: [PATCH] Improve amcheck to also check UNIQUE constraint in btree index. Pavel Borisov <pashkin.elfe@gmail.com>
Re: [PATCH] Improve amcheck to also check UNIQUE constraint in btree index. Zhihong Yu <zyu@yugabyte.com>
Re: [PATCH] Improve amcheck to also check UNIQUE constraint in btree index. Pavel Borisov <pashkin.elfe@gmail.com> 
On Thu, Apr 25, 2024 at 04:59:54PM +0400, Pavel Borisov wrote:
> 0001: Optimize speed by avoiding heap visibility checking for different
> non-deduplicated index tuples as proposed by Noah Misch
> 
> Speed measurements on my laptop using the exact method recommended by Noah
> upthread:
> Current master branch: checkunique off: 144s, checkunique on: 419s
> With patch 0001: checkunique off: 141s, checkunique on: 171s

Where is the CPU time going to make it still be 21% slower w/ checkunique on?
It's a great improvement vs. current master, but I don't have an obvious
explanation for the remaining +21%.
В списке pgsql-hackers по дате отправления
Предыдущее
От: Nathan Bossart
Дата:
Следующее
От: Alexander Korotkov
Дата:
FAQ