Postgres Pro
Downloads
Home   >   mailing lists

Re: How to deal with analyze gathering irrelevant stats - Mailing list pgsql-performance

From Michael Lewis
Subject Re: How to deal with analyze gathering irrelevant stats
Date
Msg-id CAHOFxGr1qAjO82Mox2zC_ZV7S2Uy=oZ+HTV=vOONgbnhUxQ=yg@mail.gmail.com
Whole thread Raw
In response to Re: How to deal with analyze gathering irrelevant stats  (Rémi Chatenay <remi.chatenay@doctolib.com>)
List pgsql-performance
Tree view
On Mon, Jan 11, 2021 at 9:52 AM Rémi Chatenay <remi.chatenay@doctolib.com> wrote:
I'd say it's a 1 insert for 5 - 10 updates.

As for the index on the status, it's because we have a job that runs every night that deals with conversations in specific statuses. Having a low cardinality index that changes frequently seems prone to mis-use by the system.  -> What would be an alternative ?

One option would be a partial index on another field used in that query where status in ( list_of_uncommon_statuses_queried_nightly )

Sequential scan may be perfectly fine for a nightly script though.

pgsql-performance by date:

Previous
From: Rémi Chatenay
Date:
Subject: Re: How to deal with analyze gathering irrelevant stats
Next
From: M Tarkeshwar Rao
Date:
Subject: RE: Need information on how MM frees up disk space (vaccum) after scheduled DB cleanup by BGwCronScript/BGwLogCleaner