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

From Michael Lewis
Subject Re: Index no longer being used, destroying and recreating it restores use.
Date
Msg-id CAHOFxGo6W9O9qfNk_CQ4vQ=1SFyi6R5+DyM-mpwmjSUZWPGudg@mail.gmail.com
Whole thread Raw
In response to Re: Index no longer being used, destroying and recreating it restores use.  (Koen De Groote <kdg.dev@gmail.com>)
Responses Re: Index no longer being used, destroying and recreating it restores use.  (Koen De Groote <kdg.dev@gmail.com>)
List pgsql-general
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: Tom Lane
Date:
Subject: Re: Possible improvement
Next
From: Paul van der Linden
Date:
Subject: Re: Possible improvement