Re: Temporarily very slow planning time after a big delete
Peter Geoghegan <[email protected]>
| Newsgroups | gmane.comp.db.postgresql.performance |
|---|---|
| Message-ID | <CAH2-WzmC1GXMM6E2Erg9LF3KMY4EHBQC49ERVkkbsoq3141nUw@mail.gmail.com> |
On Tue, May 21, 2019 at 11:16 AM Walter Smith <[email protected]> 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