Re: BUG #15290: Stuck Parallel Index Scan query

Поиск
Список
Период
Сортировка
От Victor Yegorov
Тема Re: BUG #15290: Stuck Parallel Index Scan query
Дата
Msg-id CAGnEboh9WhwuVWZwHDRzj7kceKfs8BZSWQK+5uSUmh7m8Q1Mkg@mail.gmail.com
обсуждение исходный текст
Ответ на BUG #15290: Stuck Parallel Index Scan query  (PG Bug reporting form <noreply@postgresql.org>)
Ответы Re: BUG #15290: Stuck Parallel Index Scan query  (Thomas Munro <thomas.munro@enterprisedb.com>)
Список pgsql-bugs
Дерево обсуждения
вс, 22 июл. 2018 г. в 21:31, PG Bug reporting form <noreply@postgresql.org>:
The following bug has been logged on the website:

Bug reference:      15290
Logged by:          Victor Yegorov
Email address:      vyegorov@gmail.com
PostgreSQL version: 10.4
Operating system:   Debian GNU/Linux 8.7 (jessie)

Some more details.
Index that was chosen for Parallel Index Scan was a partial index. And it is quite bloated:

"coubs_type_is_done_partial_simple" btree (type, is_done) WHERE type::text = 'Coub::Simple'::text
6766MB

What we did — created another, ordinary index:

"index_coubs_on_is_done_and_in_process_and_type" btree (is_done, in_process, type)
2141MB

So now planner prefers to use new index and issue is not re-appearing. Query executes within 10-20ms.
Old bloated index is still around for analysis. `amcheck` showed no issues with it, though.
 

--
Victor Yegorov

В списке pgsql-bugs по дате отправления:

Предыдущее
От: Victor Yegorov
Дата:
Сообщение: Re: BUG #15290: Stuck Parallel Index Scan query
Следующее
От: Thomas Munro
Дата:
Сообщение: Re: BUG #15290: Stuck Parallel Index Scan query