Re: How to deal with analyze gathering irrelevant stats

From: Michael Lewis <mlewis(at)entrata(dot)com>
To: Adam Brusselback <adambrusselback(at)gmail(dot)com>
Cc: Justin Pryzby <pryzby(at)telsasoft(dot)com>, Rémi Chatenay <remi(dot)chatenay(at)doctolib(dot)com>, Pgsql Performance <pgsql-performance(at)lists(dot)postgresql(dot)org>
Subject: Re: How to deal with analyze gathering irrelevant stats
Date: 2021-01-11 16:47:36
Message-ID: CAHOFxGqFjQqahK8NKOyjyjPivHkra5fFzMMCn64kYYL859VFwA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

What is the usage pattern of the conversations table? Is getting many
inserts during the day, or updates of status mostly?

Why have an index on the status column at all? My guess would be that there
are 2-10 statuses, but many many rows in the table for most of those
statuses. Having a low cardinality index that changes frequently seems
prone to mis-use by the system.

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Rémi Chatenay 2021-01-11 16:52:25 Re: How to deal with analyze gathering irrelevant stats
Previous Message Adam Brusselback 2021-01-11 16:37:33 Re: How to deal with analyze gathering irrelevant stats