mirrors/synapse
mirrors/synapse
1
0
Fork 0
mirror of https://github.com/element-hq/synapse.git synced 2025-03-31 03:45:13 +00:00
Code Activity

deploy: 0921d93dcd

Browse source
This commit is contained in:
reivilibre 2022-04-19 12:29:06 +00:00
parent c9977cd749
commit 963ebb0428
4 changed files with 4 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
develop/print.html
View file

@ -1616,7 +1616,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 (which normally happens when the main process is upgraded), to ensure the change is made safely
without any risk of reusing transaction IDs.</p> without any risk of reusing transaction IDs.</p>
<p>Deployments which do not use separate worker processes can be upgraded as normal. Similarly, <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> <details>
<summary><b>Recovering from an incorrect upgrade</b></summary> <summary><b>Recovering from an incorrect upgrade</b></summary>
<p>If the database schema is upgraded <em>without</em> stopping the worker responsible <p>If the database schema is upgraded <em>without</em> stopping the worker responsible

2
develop/searchindex.js
View file

File diff suppressed because one or more lines are too long

2
develop/searchindex.json
View file

File diff suppressed because one or more lines are too long

2
develop/upgrade.html
View file

@ -236,7 +236,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 (which normally happens when the main process is upgraded), to ensure the change is made safely
without any risk of reusing transaction IDs.</p> without any risk of reusing transaction IDs.</p>
<p>Deployments which do not use separate worker processes can be upgraded as normal. Similarly, <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> <details>
<summary><b>Recovering from an incorrect upgrade</b></summary> <summary><b>Recovering from an incorrect upgrade</b></summary>
<p>If the database schema is upgraded <em>without</em> stopping the worker responsible <p>If the database schema is upgraded <em>without</em> stopping the worker responsible