reivilibre 11e15d79b8 Fix a performance issue introduced in Synapse v1.83.0 which meant that purging rooms was very slow and database-intensive. (#15693) ... * Add indices required to efficiently validate new foreign key constraints on stream_ordering * Newsfile Signed-off-by: Olivier Wilkinson (reivilibre) <oliverw@matrix.org> --------- Signed-off-by: Olivier Wilkinson (reivilibre) <oliverw@matrix.org>		2023-05-31 14:59:56 +01:00
..
01_add_profiles_not_valid_check.sql.postgres	Add not null constraint to column full_user_id of tables profiles and user_filters (#15537)	2023-05-16 10:57:39 -07:00
02_add_user_filters_not_valid_check.sql.postgres	Add not null constraint to column full_user_id of tables profiles and user_filters (#15537)	2023-05-16 10:57:39 -07:00
03bg_populate_full_user_id_profiles.sql	Add not null constraint to column full_user_id of tables profiles and user_filters (#15537)	2023-05-16 10:57:39 -07:00
04bg_populate_full_user_id_user_filters.sql	Add not null constraint to column full_user_id of tables profiles and user_filters (#15537)	2023-05-16 10:57:39 -07:00
05thread_notifications_backfill.sql	Set thread_id column to non-null for event_push_{actions,actions_staging,summary} (#15597)	2023-05-26 13:16:08 -04:00
06thread_notifications_not_null_event_push_actions_staging.sql.postgres	Set thread_id column to non-null for event_push_{actions,actions_staging,summary} (#15597)	2023-05-26 13:16:08 -04:00
06thread_notifications_not_null_event_push_actions.sql.postgres	Set thread_id column to non-null for event_push_{actions,actions_staging,summary} (#15597)	2023-05-26 13:16:08 -04:00
06thread_notifications_not_null_event_push_summary.sql.postgres	Set thread_id column to non-null for event_push_{actions,actions_staging,summary} (#15597)	2023-05-26 13:16:08 -04:00
06thread_notifications_not_null.sql.sqlite	Set thread_id column to non-null for event_push_{actions,actions_staging,summary} (#15597)	2023-05-26 13:16:08 -04:00
14bg_indices_event_stream_ordering.sql	Fix a performance issue introduced in Synapse v1.83.0 which meant that purging rooms was very slow and database-intensive. (#15693)	2023-05-31 14:59:56 +01:00