b2c2b03079
PostgreSQL may underestimate the number of distinct `room_id`s in `event_search`, which can cause it to use table scans for queries for multiple rooms. Fix this by setting `n_distinct` on the column. Resolves #14402. Signed-off-by: Sean Quah <seanq@matrix.org> |
||
|---|---|---|
| .. | ||
| 01event_failed_pull_attempts.sql | ||
| 02add_pusher_enabled.sql | ||
| 02room_id_indexes_for_purging.sql | ||
| 03pusher_device_id.sql | ||
| 03users_approved_column.sql | ||
| 04partial_join_details.sql | ||
| 04pending_device_list_updates.sql | ||
| 05old_push_actions.sql.postgres | ||
| 05old_push_actions.sql.sqlite | ||
| 06thread_notifications_thread_id_idx.sql | ||
| 08thread_receipts_non_null.sql.postgres | ||
| 08thread_receipts_non_null.sql.sqlite | ||
| 09partial_joined_via_destination.sql | ||
| 09threads_table.sql | ||
| 10_update_sqlite_fts4_tokenizer.py | ||
| 10login_tokens.sql | ||
| 11event_search_room_id_n_distinct.sql.postgres | ||