tileradotorg/synapse
1
0
Fork 0
forked from MirrorHub/synapse
Code Pull requests Activity

In light of #8255, use BIGINTs for destination_rooms (#8256)

Browse source
This commit is contained in:
reivilibre 2020-09-04 15:07:29 +01:00 committed by GitHub
parent 17fa4c7ca7
commit 7513006b09
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 2 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

1
changelog.d/8256.misc Normal file
View file

@ -0,0 +1 @@
Track the latest event for every destination and room for catch-up after federation outage.

2
synapse/storage/databases/main/schema/delta/58/15_catchup_destination_rooms.sql
View file

@ -23,7 +23,7 @@ CREATE TABLE IF NOT EXISTS destination_rooms (
-- the ID of the room in question -- the ID of the room in question
room_id TEXT NOT NULL REFERENCES rooms (room_id), room_id TEXT NOT NULL REFERENCES rooms (room_id),
-- the stream_ordering of the event -- the stream_ordering of the event
stream_ordering INTEGER NOT NULL, stream_ordering BIGINT NOT NULL,
PRIMARY KEY (destination, room_id) PRIMARY KEY (destination, room_id)
-- We don't declare a foreign key on stream_ordering here because that'd mean -- We don't declare a foreign key on stream_ordering here because that'd mean
-- we'd need to either maintain an index (expensive) or do a table scan of -- we'd need to either maintain an index (expensive) or do a table scan of