Jesse Hallam 3016fa6010 MM-42919: avoid sequential scan on Posts (#19878) ...

On Postgres, `GetTeamsUnreadForUser` triggers a sequential scan on `Posts`. We can avoid this by querying the `Threads` table directly and only joining to `Posts` to eliminate deleted threads. (We could avoid the latter if we later denormalize `DeleteAt` onto `Threads`.)

Fixes: https://mattermost.atlassian.net/browse/MM-42919

2022-04-06 09:21:01 -03:00

..

layer_generators

Add a sleep in-between retries (#18853)

2021-10-27 19:41:21 +05:30

localcachelayer

Replace remaining GetMaster() queries (#19545)

2022-02-16 22:30:27 +05:30

opentracinglayer

MM-41260: Revamp ES/Bleve batching logic (#19841)

2022-03-31 10:46:01 +05:30

retrylayer

MM-41260: Revamp ES/Bleve batching logic (#19841)

2022-03-31 10:46:01 +05:30

searchlayer

MM-38164: Paginate the GetPostThread API (#19485)

2022-03-24 12:51:41 +05:30

searchtest

spelling: strings (#19542)

2022-02-28 15:01:00 +05:30

sqlstore

MM-42919: avoid sequential scan on Posts (#19878)

2022-04-06 09:21:01 -03:00

storetest

MM-41260: Revamp ES/Bleve batching logic (#19841)

2022-03-31 10:46:01 +05:30

timerlayer

MM-41260: Revamp ES/Bleve batching logic (#19841)

2022-03-31 10:46:01 +05:30

constants.go

MM-31063: Change constants to use CamelCase (#16608)

2021-01-04 11:32:29 +05:30

errors.go

Custom groups (#18839)

2022-02-17 12:34:39 -05:00

store.go

MM-41260: Revamp ES/Bleve batching logic (#19841)

2022-03-31 10:46:01 +05:30