Correct docs for behaviour of ALTER DATABASE .. RENAME during Hot Standby.

Actual behaviour did not match documented behaviour and we have agreed
that it should be the docs that change.

Spotted by Bernd Helmle

diff --git a/doc/src/sgml/high-availability.sgml b/doc/src/sgml/high-availability.sgml
index 211cc25d82e107ae15e1e54d4f67564dbc5868fa..9b4fa3a6d20be976cf64803bfa98da3e54626f72 100644 (file)
--- a/doc/src/sgml/high-availability.sgml
+++ b/doc/src/sgml/high-availability.sgml
@@ -1764,12 +1764,15 @@ LOG:  database system is ready to accept read only connections
    
 
    
-    Running DROP DATABASE, ALTER DATABASE ... SET
-    TABLESPACE, or ALTER DATABASE ... RENAME on the primary
+    Running DROP DATABASE or ALTER DATABASE ... SET
+    TABLESPACE on the primary
     will generate a WAL entry that will cause all users connected to that
     database on the standby to be forcibly disconnected. This action occurs
     immediately, whatever the setting of
-    max_standby_streaming_delay.
+    max_standby_streaming_delay. Note that
+    ALTER DATABASE ... RENAME does not disconnect users, which
+    in most cases will go unnoticed, though might in some cases cause a
+    program confusion if it depends in some way upon database name.