mirrors/synapse
1
0
Fork 0
mirror of https://github.com/element-hq/synapse.git synced 2024-11-21 17:15:38 +03:00
Code Issues Projects Releases Packages Wiki Activity

deploy: dfc7646504

Browse source
This commit is contained in:
reivilibre 2022-04-19 10:30:29 +00:00
parent ff862c8781
commit 2d2f2f4dfd
4 changed files with 4 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
v1.57/print.html
View file

@ -1612,7 +1612,7 @@ worker for application service traffic, <strong>it must be stopped</strong> when
(which normally happens when the main process is upgraded), to ensure the change is made safely
without any risk of reusing transaction IDs.</p>
<p>Deployments which do not use separate worker processes can be upgraded as normal. Similarly,
deployments where no applciation services are in use can be upgraded as normal.</p>
deployments where no application services are in use can be upgraded as normal.</p>
<details>
<summary><b>Recovering from an incorrect upgrade</b></summary>
<p>If the database schema is upgraded <em>without</em> stopping the worker responsible

2
v1.57/searchindex.js
View file

File diff suppressed because one or more lines are too long

2
v1.57/searchindex.json
View file

File diff suppressed because one or more lines are too long

2
v1.57/upgrade.html
View file

@ -232,7 +232,7 @@ worker for application service traffic, <strong>it must be stopped</strong> when
(which normally happens when the main process is upgraded), to ensure the change is made safely
without any risk of reusing transaction IDs.</p>
<p>Deployments which do not use separate worker processes can be upgraded as normal. Similarly,
deployments where no applciation services are in use can be upgraded as normal.</p>
deployments where no application services are in use can be upgraded as normal.</p>
<details>
<summary><b>Recovering from an incorrect upgrade</b></summary>
<p>If the database schema is upgraded <em>without</em> stopping the worker responsible