# HG changeset patch
# User Alain Mazy <am@osimis.io>
# Date 1709395169 -3600
# Node ID edd8e2d0eb9904a24ec6979dcf111ec92009e8c0
# Parent  b5f57cec7190c65e390869da440c76256e0ddb68
cont

diff -r b5f57cec7190 -r edd8e2d0eb99 Sphinx/source/plugins/postgresql.rst
--- a/Sphinx/source/plugins/postgresql.rst	Sat Mar 02 16:38:17 2024 +0100
+++ b/Sphinx/source/plugins/postgresql.rst	Sat Mar 02 16:59:29 2024 +0100
@@ -364,16 +364,19 @@
 rolling updates of the Orthanc containers when performing a DB upgrade.  All Orthanc containers should use the same version of the
 plugin, the one that is compatible with the current revision.
 
-Therefore, in complex setups, it might be simpler/safer to simply shut-down the Orthanc containers, perform the update
+Therefore, in complex setups, it might be simpler/safer to simply shut-down the Orthanc containers, perform the upgrade
 manually and then, restart the Orthanc containers with the newest version of the plugin.
 
-To upgrade manually from revision 1 to revision 2, one might run this procedure::
+To upgrade manually from revision 1 to revision 2, one might run this procedure on the existing DB::
 
   $ wget https://orthanc.uclouvain.be/hg/orthanc-databases/raw-file/default/PostgreSQL/Plugins/SQL/Upgrades/Rev1ToRev2.sql
   $ wget https://orthanc.uclouvain.be/hg/orthanc-databases/raw-file/default/PostgreSQL/Plugins/SQL/PrepareIndex.sql
   $ psql -U postgres -f Rev1ToRev2.sql
   $ psql -U postgres -f PrepareIndex.sql
 
+This procedure is identical to the one performed automatically by Orthanc when it detects that an upgraded is required.
+
+
 
 Troubleshooting
 ---------------