UPDATE reactions SET channelid = COALESCE((select channelid from posts where posts.id = reactions.postid), '') WHERE channelid='' ĬREATE INDEX CONCURRENTLY IF NOT EXISTS idx_reactions_channel_id on reactions (channelid) UPDATE Reactions SET ChannelId = COALESCE((select ChannelId from Posts where Posts.Id = Reactions.PostId), '') WHERE ChannelId="" ĬREATE INDEX idx_reactions_channel_id ON Reactions(ChannelId) LOCK=NONE ĪLTER TABLE reactions ADD COLUMN IF NOT EXISTS channelid varchar(26) NOT NULL DEFAULT '' This is fully backwards-compatible.ĪLTER TABLE Reactions ADD COLUMN ChannelId varchar(26) NOT NULL DEFAULT "" #Release notes for safari technology preview 17 upgradeYou can run the following SQL queries before the upgrade to obtain a lock on Reactions table, so that users’ reactions posted during this time won’t be reflected in the database until the migrations are complete. PostgreSQL 12M Posts, 2.5M Reactions - ~1min 18s (instance: db.r5.2xlarge) #Release notes for safari technology preview 17 PcMySQL 12M Posts, 2.5M Reactions - ~1min 34s (instance: PC with 8 cores, 16GB RAM) The following notes our test results for the schema changes: Mattermost v7.1 introduces schema changes in the form of a new column and its index. Therefore, we recommend that MaxImageResolution * MaxImageDecoderConcurrency * 24 should be less than the allocated memory for image decoding. The maximum memory of a single image is dictated by MaxImageResolution * 24 bytes. This affects the total memory consumption of the server. The default is -1, and the value indicates the number of CPUs present. A new configuration option MaxImageDecoderConcurrency indicates how many images can be decoded concurrently at once.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |