Merge pull request #5720 from matrix-org/erikj/transactions_upsert

Use upsert when updating destination retry interval
This commit is contained in:
Erik Johnston 2019-07-19 16:51:16 +01:00 committed by GitHub
commit 7704873cb8
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 21 additions and 0 deletions

1
changelog.d/5720.misc Normal file
View File

@ -0,0 +1 @@
Improve database query performance when recording retry intervals for remote hosts.

View File

@ -196,6 +196,26 @@ class TransactionStore(SQLBaseStore):
def _set_destination_retry_timings( def _set_destination_retry_timings(
self, txn, destination, retry_last_ts, retry_interval self, txn, destination, retry_last_ts, retry_interval
): ):
if self.database_engine.can_native_upsert:
# Upsert retry time interval if retry_interval is zero (i.e. we're
# resetting it) or greater than the existing retry interval.
sql = """
INSERT INTO destinations (destination, retry_last_ts, retry_interval)
VALUES (?, ?, ?)
ON CONFLICT (destination) DO UPDATE SET
retry_last_ts = EXCLUDED.retry_last_ts,
retry_interval = EXCLUDED.retry_interval
WHERE
EXCLUDED.retry_interval = 0
OR destinations.retry_interval < EXCLUDED.retry_interval
"""
txn.execute(sql, (destination, retry_last_ts, retry_interval))
return
self.database_engine.lock_table(txn, "destinations") self.database_engine.lock_table(txn, "destinations")
# We need to be careful here as the data may have changed from under us # We need to be careful here as the data may have changed from under us