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 ?
On Mon, Jan 11, 2021 at 5:48 PM Michael Lewis <mlewis@entrata.com> wrote:
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.
