From: Simon Riggs <simon@2ndQuadrant.com>
Date: Tue, 5 Oct 2010 23:20:54 +0000 (+0100)
Subject: Correct docs for behaviour of ALTER DATABASE .. RENAME during Hot Standby.
X-Git-Tag: REL9_0_2~76
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=7887db612cefcc9f2648f3248cba1f3904c80b3b;p=postgresql

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 16bd9d1e5b..a4be8276be 100644
--- 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
    </para>
 
    <para>
-    Running <command>DROP DATABASE</>, <command>ALTER DATABASE ... SET
-    TABLESPACE</>, or <command>ALTER DATABASE ... RENAME</> on the primary
+    Running <command>DROP DATABASE</> or <command>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
-    <varname>max_standby_streaming_delay</>.
+    <varname>max_standby_streaming_delay</>. Note that
+    <command>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.
    </para>
 
    <para>