Re: SELECT DISTINCT chooses parallel seqscan instead of indexscan on huge table with 1000 partitions

Поиск
Список
Период
Сортировка
Искать
От
Dimitrios Apostolou
Тема
Re: SELECT DISTINCT chooses parallel seqscan instead of indexscan on huge table with 1000 partitions
Дата
в 16:14:45
Msg-id
5dfcb84a-2d32-8dde-772b-4305a7468774@gmx.net
Ответ на
Re: SELECT DISTINCT chooses parallel seqscan instead of indexscan on huge table with 1000 partitions (Dimitrios Apostolou)
Список
Дерево обсуждения
SELECT DISTINCT chooses parallel seqscan instead of indexscan on huge table with 1000 partitions Dimitrios Apostolou <jimis@gmx.net>
Re: SELECT DISTINCT chooses parallel seqscan instead of indexscan on huge table with 1000 partitions Dimitrios Apostolou <jimis@gmx.net>
Re: SELECT DISTINCT chooses parallel seqscan instead of indexscan on huge table with 1000 partitions Dimitrios Apostolou <jimis@gmx.net>
Re: SELECT DISTINCT chooses parallel seqscan instead of indexscan on huge table with 1000 partitions Dimitrios Apostolou <jimis@gmx.net>
Re: SELECT DISTINCT chooses parallel seqscan instead of indexscan on huge table with 1000 partitions Dimitrios Apostolou <jimis@gmx.net>
Re: SELECT DISTINCT chooses parallel seqscan instead of indexscan on huge table with 1000 partitions Dimitrios Apostolou <jimis@gmx.net>
Re: SELECT DISTINCT chooses parallel seqscan instead of indexscan on huge table with 1000 partitions David Rowley <dgrowleyml@gmail.com>
Re: SELECT DISTINCT chooses parallel seqscan instead of indexscan on huge table with 1000 partitions Dimitrios Apostolou <jimis@gmx.net>
Re: SELECT DISTINCT chooses parallel seqscan instead of indexscan on huge table with 1000 partitions David Rowley <dgrowleyml@gmail.com>
Re: SELECT DISTINCT chooses parallel seqscan instead of indexscan on huge table with 1000 partitions Dimitrios Apostolou <jimis@gmx.net>
Re: SELECT DISTINCT chooses parallel seqscan instead of indexscan on huge table with 1000 partitions David Rowley <dgrowleyml@gmail.com>
Re: SELECT DISTINCT chooses parallel seqscan instead of indexscan on huge table with 1000 partitions David Rowley <dgrowleyml@gmail.com>
Re: SELECT DISTINCT chooses parallel seqscan instead of indexscan on huge table with 1000 partitions Dimitrios Apostolou <jimis@gmx.net>
Re: SELECT DISTINCT chooses parallel seqscan instead of indexscan on huge table with 1000 partitions Dimitrios Apostolou <jimis@gmx.net>
Re: SELECT DISTINCT chooses parallel seqscan instead of indexscan on huge table with 1000 partitions David Rowley <dgrowleyml@gmail.com>
Re: SELECT DISTINCT chooses parallel seqscan instead of indexscan on huge table with 1000 partitions David Rowley <dgrowleyml@gmail.com>
Re: SELECT DISTINCT chooses parallel seqscan instead of indexscan on huge table with 1000 partitions Dimitrios Apostolou <jimis@gmx.net>
Re: SELECT DISTINCT chooses parallel seqscan instead of indexscan on huge table with 1000 partitions Dimitrios Apostolou <jimis@gmx.net>
Re: SELECT DISTINCT chooses parallel seqscan instead of indexscan on huge table with 1000 partitions Dimitrios Apostolou <jimis@gmx.net>
Re: SELECT DISTINCT chooses parallel seqscan instead of indexscan on huge table with 1000 partitions David Rowley <dgrowleyml@gmail.com> 
On Tue, 14 May 2024, Dimitrios Apostolou wrote:
>
> It took long but if finished:
>
> ANALYZE
> Time: 19177398.025 ms (05:19:37.398)

I see now that default_statistics_target is globally set to 500, so this
is probably the reason it took so long. I guess with the default of 100,
it would take approximately one hour. This is much better to have in a
cron job. :-)

Dimitris
В списке pgsql-general по дате отправления
Предыдущее
От: Muhammad Imtiaz
Дата:
Сообщение: Re: Valid until
Следующее
От: Dimitrios Apostolou
Дата:
FAQ