Docs for behaviour change of drop database during Hot Standby
authorSimon Riggs <simon@2ndquadrant.com>
Sun, 10 Jan 2010 16:27:27 +0000 (16:27 +0000)
committerSimon Riggs <simon@2ndquadrant.com>
Sun, 10 Jan 2010 16:27:27 +0000 (16:27 +0000)
Adding missing docs for previous Hot Standby patch.

doc/src/sgml/backup.sgml

index 1276c3987c48c1e35d1e42cd3b0cd36082deb3ef..f29fb4f08fe96e9e81cd83d4ba99fd62b991f9b0 100644 (file)
@@ -2169,7 +2169,8 @@ if (!triggered)
        </listitem>
        <listitem>
         <para>
-         Dropping databases on the primary while that role is connected on standby.
+         Dropping databases on the primary while users are connected to that
+         database on the standby.
         </para>
        </listitem>
        <listitem>
@@ -2542,7 +2543,8 @@ LOG:  database system is ready to accept read only connections
     Running <command>DROP DATABASE</>, <command>ALTER DATABASE ... SET TABLESPACE</>,
     or <command>ALTER DATABASE ... RENAME</> on primary will generate a log message
     that will cause all users connected to that database on the standby to be
-    forcibly disconnected, once <varname>max_standby_delay</> has been reached.
+    forcibly disconnected. This action occurs immediately, whatever the setting of
+   <varname>max_standby_delay</>.
    </para>
 
    <para>