Re: Index no longer being used, destroying and recreating it restores use. - Mailing list pgsql-general

From Koen De Groote
Subject Re: Index no longer being used, destroying and recreating it restores use.
Date
Msg-id CAGbX52G_OvW0Z7C7-gWucL+iypaJh-x9zcG6FkB7K0oCsnZ1oA@mail.gmail.com
Whole thread Raw
In response to Re: Index no longer being used, destroying and recreating it restores use.  (Michael Lewis <mlewis@entrata.com>)
Responses Re: Index no longer being used, destroying and recreating it restores use.  (Koen De Groote <kdg.dev@gmail.com>)
List pgsql-general
I'll attempt this next week.

On Fri, Jun 5, 2020, 21:11 Michael Lewis <mlewis@entrata.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.

pgsql-general by date:

Previous
From: Michel Pelletier
Date:
Subject: Re: Should I enforce ssl/local socket use?
Next
From: Tim Cross
Date:
Subject: Re: Should I enforce ssl/local socket use?