Set thread_id column to non-null for event_push_{actions,actions_staging,summary} (#15350)
Clean-up from adding the thread_id column, which was initially null but backfilled with values. It is desirable to require it to now be non-null. In addition to altering this column to be non-null, we clean up obsolete background jobs, indexes, and just-in-time updating code.
Showing
- changelog.d/15350.misc 1 addition, 0 deletionschangelog.d/15350.misc
- synapse/storage/databases/main/event_push_actions.py 0 additions, 240 deletionssynapse/storage/databases/main/event_push_actions.py
- synapse/storage/schema/__init__.py 3 additions, 3 deletionssynapse/storage/schema/__init__.py
- synapse/storage/schema/main/delta/74/02thread_notifications_backfill.sql 28 additions, 0 deletions.../schema/main/delta/74/02thread_notifications_backfill.sql
- synapse/storage/schema/main/delta/74/03thread_notifications_not_null.sql.postgres 23 additions, 0 deletions...ain/delta/74/03thread_notifications_not_null.sql.postgres
- synapse/storage/schema/main/delta/74/03thread_notifications_not_null.sql.sqlite 99 additions, 0 deletions.../main/delta/74/03thread_notifications_not_null.sql.sqlite
Loading