Commit message (Collapse) | Author | Files | Lines | ||
---|---|---|---|---|---|
2018-02-16 | (Really) fix tablescan of event_push_actions on purge | Richard van der Hoff | 1 | -1/+0 | |
commit 278d21b5 added new code to avoid the tablescan, but didn't remove the old :/ | |||||
2018-02-16 | Fix typo of double is_highlight | Erik Johnston | 1 | -1/+1 | |
2018-02-16 | Comments | Erik Johnston | 3 | -1/+9 | |
2018-02-15 | Fix unit test | Erik Johnston | 1 | -4/+6 | |
2018-02-15 | Ensure that we delete staging push actions on errors | Erik Johnston | 2 | -3/+25 | |
2018-02-15 | Remove context.push_actions | Erik Johnston | 5 | -20/+11 | |
2018-02-15 | Update event_push_actions table from staging table | Erik Johnston | 2 | -22/+39 | |
2018-02-15 | Store push actions in staging area | Erik Johnston | 3 | -0/+54 | |
2018-02-15 | Don't serialize current state over replication | Erik Johnston | 3 | -8/+51 | |
2018-02-15 | Fix state group storage bug in workers | Erik Johnston | 1 | -41/+41 | |
We needed to move `_count_state_group_hops_txn` to the StateGroupWorkerStore. | |||||
2018-02-15 | Don't log errors propogated from send_event | Erik Johnston | 1 | -1/+10 | |
2018-02-14 | purge_history: fix sqlite syntax error | Richard van der Hoff | 1 | -1/+4 | |
apparently sqlite insists on indexes being named | |||||
2018-02-14 | purge_history: handle sqlite asshattery | Richard van der Hoff | 1 | -19/+27 | |
apparently creating a temporary table commits the transaction. because that's a useful thing. | |||||
2018-02-14 | remove overzealous exception handling | Richard van der Hoff | 1 | -18/+10 | |
2018-02-14 | purge_history: fix index use | Richard van der Hoff | 1 | -0/+14 | |
event_push_actions doesn't have an index on event_id, so we need to specify room_id. | |||||
2018-02-14 | Rework event purge to use a temporary table | Richard van der Hoff | 1 | -35/+58 | |
... which should speed things up by reducing the amount of data being shuffled across the connection | |||||
2018-02-13 | Update docs | Erik Johnston | 1 | -1/+4 | |
2018-02-13 | Fix log message in purge_history | Richard van der Hoff | 1 | -2/+1 | |
(we don't just remove remote events) | |||||
2018-02-13 | move search reindex to schema 47 | Richard van der Hoff | 2 | -1/+1 | |
We're up to schema v47 on develop now, so this will have to go in there to have an effect. This might cause an error if somebody has already run it in the v46 guise, and runs it again in the v47 guise, because it will cause a duplicate entry in the bbackground_updates table. On the other hand, the entry is removed once it is complete, and it is unlikely that anyone other than matrix.org has run it on v46. The update itself is harmless to re-run because it deliberately copes with the index already existing. | |||||
2018-02-13 | GIN reindex: Fix syntax errors, improve exception handling | Richard van der Hoff | 1 | -13/+27 | |
2018-02-13 | style nit | Richard van der Hoff | 1 | -1/+1 | |
2018-02-13 | Fix typos in purge api & doc | Richard van der Hoff | 2 | -4/+2 | |
* It's supposed to be purge_local_events, not ..._history * Fix the doc to have valid json | |||||
2018-02-12 | Update workers docs to include http port | Erik Johnston | 1 | -5/+20 | |
2018-02-09 | purge: move room_depth update to end | Richard van der Hoff | 1 | -6/+12 | |
... to avoid locking the table for too long | |||||
2018-02-09 | delete_local_events for purge_history | Richard van der Hoff | 5 | -15/+67 | |
Add a flag which makes the purger delete local events | |||||
2018-02-09 | purge: Move cache invalidation to more appropriate place | Richard van der Hoff | 1 | -4/+4 | |
it was a bit of a non-sequitur there | |||||
2018-02-09 | bump purge logging to info | Richard van der Hoff | 1 | -13/+14 | |
this thing takes ages and the only sign of any progress is the logs, so having some logs is useful. | |||||
2018-02-09 | rename delete_old_state -> purge_history | Richard van der Hoff | 2 | -8/+8 | |
(beacause it deletes more than state) | |||||
2018-02-07 | Tell storage providers about new file so they can upload | Erik Johnston | 1 | -0/+6 | |
2018-02-07 | Add note in docs/workers.rst | Erik Johnston | 1 | -0/+11 | |
2018-02-07 | Move presence handling into handle_new_client_event | Erik Johnston | 1 | -6/+6 | |
As we want to have it run on the main synapse instance | |||||
2018-02-07 | Add event_creator worker | Erik Johnston | 3 | -1/+190 | |
2018-02-07 | Add replication http endpoint for event sending | Erik Johnston | 8 | -13/+304 | |
2018-02-07 | Remove pointless ratelimit check | Erik Johnston | 1 | -5/+0 | |
The intention was for the check to be called as early as possible in the request, but actually was called just before the main ratelimit check, so was fairly pointless. | |||||
2018-02-06 | Update copyright | Erik Johnston | 6 | -1/+6 | |
2018-02-06 | s/_create_new_client_event/create_new_client_event/ | Erik Johnston | 4 | -12/+12 | |
2018-02-06 | Store state groups separately from events (#2784) | Erik Johnston | 12 | -189/+326 | |
* Split state group persist into seperate storage func * Add per database engine code for state group id gen * Move store_state_group to StateReadStore This allows other workers to use it, and so resolve state. * Hook up store_state_group * Fix tests * Rename _store_mult_state_groups_txn * Rename StateGroupReadStore * Remove redundant _have_persisted_state_group_txn * Update comments * Comment compute_event_context * Set start val for state_group_id_seq ... otherwise we try to recreate old state groups * Update comments * Don't store state for outliers * Update comment * Update docstring as state groups are ints | |||||
2018-02-05 | Use StateResolutionHandler to resolve state in persist events | Richard van der Hoff | 1 | -48/+24 | |
... and thus benefit (hopefully) from its cache. | |||||
2018-02-05 | Flatten _get_new_state_after_events | Richard van der Hoff | 1 | -44/+46 | |
rejig the if statements to simplify the logic and reduce indentation | |||||
2018-02-05 | Check that events being persisted have state_group | Richard van der Hoff | 1 | -4/+9 | |
2018-02-05 | Add event_map param to resolve_state_groups | Richard van der Hoff | 2 | -4/+31 | |
2018-02-05 | Remove redundant return value from _calculate_state_delta | Richard van der Hoff | 1 | -10/+23 | |
we already have the state from _get_new_state_after_events, so returning it from _calculate_state_delta is just confusing. | |||||
2018-02-05 | Factor out common code for search insert | Richard van der Hoff | 1 | -33/+62 | |
we can reuse the same code as is used for event insert, for doing the background index population. | |||||
2018-02-05 | Updates tests | Erik Johnston | 2 | -8/+6 | |
2018-02-05 | Update places where we create events | Erik Johnston | 7 | -38/+42 | |
2018-02-05 | Split event creation into a separate handler | Erik Johnston | 1 | -146/+160 | |
2018-02-05 | Move store_event_search_txn to SearchStore | Richard van der Hoff | 2 | -35/+41 | |
... as a precursor to making event storing and doing the bg update share some code. | |||||
2018-02-05 | report metrics on number of cache evictions | Richard van der Hoff | 5 | -5/+56 | |
2018-02-05 | Fix broken unit test for media storage | Erik Johnston | 1 | -1/+6 | |
2018-02-05 | Add .vscode to gitignore | Erik Johnston | 1 | -0/+2 | |
2018-02-04 | Factor out common code for search insert | Richard van der Hoff | 1 | -33/+56 | |
we can reuse the same code as is used for event insert, for doing the background index population. | |||||
2018-02-03 | Clean up work_mem handling | Richard van der Hoff | 1 | -11/+41 | |
Add some comments and improve exception handling when twiddling work_mem for the search update | |||||
2018-02-03 | Move store_event_search_txn to SearchStore | Richard van der Hoff | 2 | -37/+43 | |
... as a precursor to making event storing and doing the bg update share some code. | |||||
2018-02-02 | Reinstate event_search_postgres_gist handler | Richard van der Hoff | 3 | -6/+31 | |
People may have queued updates for this, so we can't just delete it. | |||||
2018-02-02 | Handle url_previews with no content-type | Richard van der Hoff | 1 | -21/+34 | |
avoid failing with an exception if the remote server doesn't give us a Content-Type header. Also, clean up the exception handling a bit. | |||||
2018-02-01 |