Re: Index no longer being used, destroying and recreating it restores use.

From: Koen De Groote <kdg(dot)dev(at)gmail(dot)com>
To: Michael Lewis <mlewis(at)entrata(dot)com>
Cc: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL General <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: Index no longer being used, destroying and recreating it restores use.
Date: 2020-06-06 22:45:46
Message-ID: CAGbX52G_OvW0Z7C7-gWucL+iypaJh-x9zcG6FkB7K0oCsnZ1oA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

I'll attempt this next week.

On Fri, Jun 5, 2020, 21:11 Michael Lewis <mlewis(at)entrata(dot)com> wrote:

> Those row estimates are pretty far off.
>
> Standard indexes and partial indexes don't get custom statistics created
> on them, but functional indexes do. I wonder if a small function
> needs_backup( shouldbebackedup, backupperformed ) and an index created on
> that function would nicely alleviate the pain. I would expect PG12 and
> extended statistics of type MCVs would bypass the need for that work around
> though.
>

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tim Cross 2020-06-07 00:32:39 Re: Should I enforce ssl/local socket use?
Previous Message Michel Pelletier 2020-06-06 21:09:52 Re: Should I enforce ssl/local socket use?