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

From: Michael Lewis <mlewis(at)entrata(dot)com>
To: Koen De Groote <kdg(dot)dev(at)gmail(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-05 19:10:37
Message-ID: CAHOFxGo6W9O9qfNk_CQ4vQ=1SFyi6R5+DyM-mpwmjSUZWPGudg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Paul van der Linden 2020-06-05 19:46:42 Re: Possible improvement
Previous Message Tom Lane 2020-06-05 19:02:34 Re: Possible improvement