mirror of
https://mau.dev/maunium/synapse.git
synced 2024-09-02 23:52:00 +00:00
0d1d3e0708
Fixes #11887 hopefully. The core change here is that `event_push_summary` now holds a summary of counts up until a much more recent point, meaning that the range of rows we need to count in `event_push_actions` is much smaller. This needs two major changes: 1. When we get a receipt we need to recalculate `event_push_summary` rather than just delete it 2. The logic for deleting `event_push_actions` is now divorced from calculating `event_push_summary`. In future it would be good to calculate `event_push_summary` while we persist a new event (it should just be a case of adding one to the relevant rows in `event_push_summary`), as that will further simplify the get counts logic and remove the need for us to periodically update `event_push_summary` in a background job.
39 lines
1.5 KiB
SQL
39 lines
1.5 KiB
SQL
/* Copyright 2017 OpenMarket Ltd
|
|
*
|
|
* Licensed under the Apache License, Version 2.0 (the "License");
|
|
* you may not use this file except in compliance with the License.
|
|
* You may obtain a copy of the License at
|
|
*
|
|
* http://www.apache.org/licenses/LICENSE-2.0
|
|
*
|
|
* Unless required by applicable law or agreed to in writing, software
|
|
* distributed under the License is distributed on an "AS IS" BASIS,
|
|
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
* See the License for the specific language governing permissions and
|
|
* limitations under the License.
|
|
*/
|
|
|
|
-- Aggregate of notification counts up to `stream_ordering`, including those
|
|
-- that may have been deleted out of the main event_push_actions table. This
|
|
-- count does not include those that were highlights, as they remain in the
|
|
-- event_push_actions table.
|
|
CREATE TABLE event_push_summary (
|
|
user_id TEXT NOT NULL,
|
|
room_id TEXT NOT NULL,
|
|
notif_count BIGINT NOT NULL,
|
|
stream_ordering BIGINT NOT NULL
|
|
);
|
|
|
|
CREATE INDEX event_push_summary_user_rm ON event_push_summary(user_id, room_id);
|
|
|
|
|
|
-- The stream ordering up to which we have aggregated the event_push_actions
|
|
-- table into event_push_summary
|
|
CREATE TABLE event_push_summary_stream_ordering (
|
|
Lock CHAR(1) NOT NULL DEFAULT 'X' UNIQUE, -- Makes sure this table only has one row.
|
|
stream_ordering BIGINT NOT NULL,
|
|
CHECK (Lock='X')
|
|
);
|
|
|
|
INSERT INTO event_push_summary_stream_ordering (stream_ordering) VALUES (0);
|