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:17:31
Message-ID: CAH2-WzmC1GXMM6E2Erg9LF3KMY4EHBQC49ERVkkbsoq3141nUw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

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

Is it a very low cardinality index? In other words, is the total
number of distinct keys rather low? Not just at any given time, but
over time?

--
Peter Geoghegan

In response to

Responses

Browse pgsql-performance by date

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