mirror of
https://github.com/discourse/discourse.git
synced 2025-02-28 22:56:39 +08:00
15f036bafa
* DEV: Migrate notifications#id to bigint (#28444) The `notifications.id` column is the most probable column to run out of values. This is because it is an `int` column that has only 2147483647 values and many notifications are generated on a regular basis in an active community. This commit migrates the column to `bigint`. These migrations do not use `ALTER TABLE ... COLUMN ... TYPE` in order to avoid the `ACCESS EXCLUSIVE` lock on the entire table. Instead, they create a new `bigint` column, copy the values to the new column and then sets the new column as primary key. Related columns (see `user_badges`, `shelved_notifications`) will be migrated in a follow-up commit. * DEV: Fix bigint notifications id migration to deal with public schema (#28538) Follow up to 799a45a291e9f2bd94278f565e58874458768079 * DEV: Migrate shelved_notifications#notification_id to bigint (#28549) DEV: Migrate shelved_notifications#notification_id to bigint The `notifications.id` has been migrated to `bigint` in previous commit 799a45a291e9f2bd94278f565e58874458768079. * DEV: Fix annotations (#28569) Follow-up to ec8ba5a0b9ff8dbefae74d6ec4f08dc13e418c6b * DEV: Migrate user_badges#notification_id to bigint (#28546) The `notifications.id` has been migrated to bigint in previous commit 799a45a291e9f2bd94278f565e58874458768079. This commit migrates one of the related columns, `user_badges.notification_id`, to `bigint`. * DEV: Migrate `User#seen_notification_id` to `bigint` (#28572) `Notification#id` was migrated to `bigint` in 799a45a291e9f2bd94278f565e58874458768079 * DEV: Migrate `Chat::NotificationMention#notification_id` to `bigint` (#28571) `Notification#id` was migrated to `bigint` in 799a45a291e9f2bd94278f565e58874458768079 --------- Co-authored-by: Alan Guo Xiang Tan <gxtan1990@gmail.com>