# HG changeset patch
# User Alain Mazy <am@osimis.io>
# Date 1709571852 -3600
# Node ID 69a318b7a58ea782c2fad6ce2ea35b2b63edd582
# Parent  edd8e2d0eb9904a24ec6979dcf111ec92009e8c0
PG: schema

diff -r edd8e2d0eb99 -r 69a318b7a58e Sphinx/source/plugins/postgresql.rst
--- a/Sphinx/source/plugins/postgresql.rst	Sat Mar 02 16:59:29 2024 +0100
+++ b/Sphinx/source/plugins/postgresql.rst	Mon Mar 04 18:04:12 2024 +0100
@@ -367,7 +367,8 @@
 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 on the existing DB::
+To upgrade manually from revision 1 to revision 2, one might run this procedure on the existing DB (note: make
+sur to select the correct DB and schema (Orthanc is using the default ``public`` shema))::
 
   $ 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