| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Use autocommit mode for single statement DB functions. (#8542) | Erik Johnston | 2020-10-14 | 1 | -31/+45 |
| | | | | | | | | | | | | | | Autocommit means that we don't wrap the functions in transactions, and instead get executed directly. Introduced in #8456. This will help: 1. reduce the number of `could not serialize access due to concurrent delete` errors that we see (though there are a few functions that often cause serialization errors that we don't fix here); 2. improve the DB performance, as it no longer needs to deal with the overhead of `REPEATABLE READ` isolation levels; and 3. improve wall clock speed of these functions, as we no longer need to send `BEGIN` and `COMMIT` to the DB. Some notes about the differences between autocommit mode and our default `REPEATABLE READ` transactions: 1. Currently `autocommit` only applies when using PostgreSQL, and is ignored when using SQLite (due to silliness with [Twisted DB classes](https://twistedmatrix.com/trac/ticket/9998)). 2. Autocommit functions may get retried on error, which means they can get applied *twice* (or more) to the DB (since they are not in a transaction the previous call would not get rolled back). This means that the functions need to be idempotent (or otherwise not care about being called multiple times). Read queries, simple deletes, and updates/upserts that replace rows (rather than generating new values from existing rows) are all idempotent. 3. Autocommit functions no longer get executed in [`REPEATABLE READ`](https://www.postgresql.org/docs/current/transaction-iso.html) isolation level, and so data can change queries, which is fine for single statement queries. | ||||
| * | Move additional tasks to the background worker (#8458) | Patrick Cloke | 2020-10-07 | 1 | -20/+22 |
| | | |||||
| * | Catch-up after Federation Outage (bonus): Catch-up on Synapse Startup (#8322) | reivilibre | 2020-09-18 | 1 | -2/+64 |
| | | | | | | | | | | | Signed-off-by: Olivier Wilkinson (reivilibre) <olivier@librepush.net> Co-authored-by: Patrick Cloke <clokep@users.noreply.github.com> * Fix _set_destination_retry_timings This came about because the code assumed that retry_interval could not be NULL — which has been challenged by catch-up. | ||||
| * | Simplify super() calls to Python 3 syntax. (#8344) | Patrick Cloke | 2020-09-18 | 1 | -1/+1 |
| | | | | | | | | This converts calls like super(Foo, self) -> super(). Generated with: sed -i "" -Ee 's/super\([^\(]+\)/super()/g' **/*.py | ||||
| * | Catch-up after Federation Outage (split, 4): catch-up loop (#8272) | reivilibre | 2020-09-15 | 1 | -1/+42 |
| | | |||||
| * | Catch up after Federation Outage (split, 2): Track last successful stream ↵ | reivilibre | 2020-09-04 | 1 | -0/+38 |
| | | | | | | ordering after transmission (#8247) Co-authored-by: Richard van der Hoff <1389908+richvdh@users.noreply.github.com> | ||||
| * | Catch-up after Federation Outage (split, 1) (#8230) | reivilibre | 2020-09-04 | 1 | -3/+63 |
| | | | | Signed-off-by: Olivier Wilkinson (reivilibre) <olivier@librepush.net> | ||||
| * | Convert additional database code to async/await. (#8195) | Patrick Cloke | 2020-08-28 | 1 | -16/+23 |
| | | |||||
| * | Convert calls of async database methods to async (#8166) | Patrick Cloke | 2020-08-27 | 1 | -8/+10 |
| | | |||||
| * | Convert appservice, group server, profile and more databases to async (#8066) | Patrick Cloke | 2020-08-12 | 1 | -5/+2 |
| | | |||||
| * | Rename database classes to make some sense (#8033) | Erik Johnston | 2020-08-05 | 1 | -0/+269 |
 |
index : matrix/thirdparty/synapse.git | |
| Unnamed repository; edit this file 'description' to name the repository. |
| summary refs log tree commit diff |