From e48fe601ff6aa207d38c73c7a39d362a17c9ed03 Mon Sep 17 00:00:00 2001 From: Daniel Gustafsson Date: Thu, 19 Nov 2026 21:35:09 +0100 Subject: [PATCH v2] doc: Document that pg_upgrade --check isn't read-only Reviewed-by: Robert Haas Discussion: https://postgr.es/m/19908-3db6f3c4f2febdcf@postgresql.org --- doc/src/sgml/ref/pgupgrade.sgml | 15 ++++++++++++++- 1 file changed, 14 insertions(+), 1 deletion(-) diff --git a/doc/src/sgml/ref/pgupgrade.sgml b/doc/src/sgml/ref/pgupgrade.sgml index e4e8c02e6d6..2037084c21b 100644 --- a/doc/src/sgml/ref/pgupgrade.sgml +++ b/doc/src/sgml/ref/pgupgrade.sgml @@ -106,7 +106,8 @@ PostgreSQL documentation - check clusters only, don't change any data + check compatibility of clusters only, but don't perform + the upgrade @@ -604,6 +605,18 @@ pg_upgrade.exe pg_upgrade requires write permission in the current directory. + + + Note that, when tbe is used, + pg_upgrade will start and stop the old + cluster, unless it is already running. It is, therefore, not a strictly + read-only operation, and must only be performed in a context where the + old server is accessible, and from which starting and stopping it is safe. + If the old cluster is already running it will however not be stopped as + part of . + + + Obviously, no one should be accessing the clusters during the upgrade. pg_upgrade defaults to running servers -- 2.39.3 (Apple Git-146)