Re: How to deal with analyze gathering irrelevant stats

Поиск
Список
Период
Сортировка
От Michael Lewis
Тема Re: How to deal with analyze gathering irrelevant stats
Дата
Msg-id CAHOFxGr1qAjO82Mox2zC_ZV7S2Uy=oZ+HTV=vOONgbnhUxQ=yg@mail.gmail.com
обсуждение исходный текст
Ответ на Re: How to deal with analyze gathering irrelevant stats  (Rémi Chatenay <remi.chatenay@doctolib.com>)
Список pgsql-performance
Дерево обсуждения
On Mon, Jan 11, 2021 at 9:52 AM Rémi Chatenay <remi.chatenay@doctolib.com> wrote:
I'd say it's a 1 insert for 5 - 10 updates.

As for the index on the status, it's because we have a job that runs every night that deals with conversations in specific statuses. Having a low cardinality index that changes frequently seems prone to mis-use by the system.  -> What would be an alternative ?

One option would be a partial index on another field used in that query where status in ( list_of_uncommon_statuses_queried_nightly )

Sequential scan may be perfectly fine for a nightly script though.

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

Предыдущее
От: Rémi Chatenay
Дата:
Сообщение: Re: How to deal with analyze gathering irrelevant stats
Следующее
От: M Tarkeshwar Rao
Дата:
Сообщение: RE: Need information on how MM frees up disk space (vaccum) after scheduled DB cleanup by BGwCronScript/BGwLogCleaner