From 2d2f2f4dfda604fa4ee1856e2064db1a19f0df30 Mon Sep 17 00:00:00 2001 From: reivilibre Date: Tue, 19 Apr 2022 10:30:29 +0000 Subject: deploy: dfc7646504cef3e4ff396c36089e1c6f1b1634de --- v1.57/print.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'v1.57/print.html') diff --git a/v1.57/print.html b/v1.57/print.html index 3104a8dec3..4c4d3b1b0e 100644 --- a/v1.57/print.html +++ b/v1.57/print.html @@ -1612,7 +1612,7 @@ worker for application service traffic, it must be stopped when (which normally happens when the main process is upgraded), to ensure the change is made safely without any risk of reusing transaction IDs.

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.

+deployments where no application services are in use can be upgraded as normal.

Recovering from an incorrect upgrade

If the database schema is upgraded without stopping the worker responsible -- cgit 1.5.1