Re: Temporarily very slow planning time after a big delete

Поиск
Список
Период
Сортировка
От Walter Smith
Тема Re: Temporarily very slow planning time after a big delete
Дата
Msg-id CAOERZXj4urxzKQF98hC-qPfsyL9ix9ucfKCH5iT3=unizwz1nA@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Temporarily very slow planning time after a big delete  (Peter Geoghegan <pg@bowt.ie>)
Ответы Re: Temporarily very slow planning time after a big delete  (Peter Geoghegan <pg@bowt.ie>)
Список pgsql-performance
Дерево обсуждения
On Tue, May 21, 2019 at 11:15 AM Peter Geoghegan <pg@bowt.ie> wrote:
On Tue, May 21, 2019 at 11:12 AM Walter Smith <walter@carezone.com> wrote
> I did a VACUUM overnight and got the following. The thing that stands out to me is that one index (index_unproc_notifications_on_notifiable_type) took 100x longer to scan than the others. That's not the index used in the slow query, though.

What columns are indexed by
index_unproc_notifications_on_notifiable_type, and what are their
datatypes?

It occurs to me that is a somewhat unusual index -- it tracks unprocessed notifications so it gets an insert and delete for every row, and is normally almost empty.

Index "public.index_unproc_notifications_on_notifiable_type"
     Column      |          Type          |   Definition
-----------------+------------------------+-----------------
 notifiable_type | character varying(255) | notifiable_type
btree, for table "public.notifications", predicate (processed = false)

Thanks,
Walter

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

Предыдущее
От: Peter Geoghegan
Дата:
Сообщение: Re: Temporarily very slow planning time after a big delete
Следующее
От: Peter Geoghegan
Дата:
Сообщение: Re: Temporarily very slow planning time after a big delete