Re: CPU Consuming query. Sequential scan despite indexing.

Поиск
Список
Период
Сортировка
От Michael Lewis
Тема Re: CPU Consuming query. Sequential scan despite indexing.
Дата
Msg-id CAHOFxGpQBgMHV67wcYd4Kz6SeCPYd3KgSx0Hi4EaQtjQDZXqUw@mail.gmail.com
обсуждение исходный текст
Ответ на CPU Consuming query. Sequential scan despite indexing.  (aditya desai <admad123@gmail.com>)
Список pgsql-performance
What version by the way? Do you get a faster execution if you disable sequential scan? Or set parallel workers per gather to 0? Your estimates look decent as do cache hits, so other than caching data or upgrading hardware, not sure what else there is to be done.

Although... you are hitting 70k blocks to read only 612k rows? Are these job records very wide perhaps, or do you need to do some vacuuming? Perhaps autovacuum is not keeping up and you could use some repacking or vacuum full if/when you can afford downtime. If you create a temp table copy of the job table, how does the size compare to the live table?

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

Предыдущее
От: aditya desai
Дата:
Сообщение: CPU Consuming query. Sequential scan despite indexing.
Следующее
От: Laurenz Albe
Дата:
Сообщение: Re: CPU Consuming query. Sequential scan despite indexing.