Re: Temporarily very slow planning time after a big delete

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: walter(at)carezone(dot)com
Cc: David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-performance(at)lists(dot)postgresql(dot)org
Subject: Re: Temporarily very slow planning time after a big delete
Date: 2019-05-21 18:15:07
Message-ID: CAH2-WzkdMf=6P0Dd9rN5dz_JFgjWE0DRCJLQkzoYw=Gw76Jx6Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Tue, May 21, 2019 at 11:12 AM Walter Smith <walter(at)carezone(dot)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?

--
Peter Geoghegan

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Walter Smith 2019-05-21 18:16:05 Re: Temporarily very slow planning time after a big delete
Previous Message Walter Smith 2019-05-21 18:12:32 Re: Temporarily very slow planning time after a big delete