Docs for behaviour change of drop database during Hot Standby

Adding missing docs for previous Hot Standby patch.

diff --git a/doc/src/sgml/backup.sgml b/doc/src/sgml/backup.sgml
index c03d8088fcbe42fd6fa256f95aea4314374b7e77..a666e53bc3b0b21cd677a53f3ca154b3f8986710 100644 (file)
--- a/doc/src/sgml/backup.sgml
+++ b/doc/src/sgml/backup.sgml
@@ -1,4 +1,4 @@
-
+
 
 
  Backup and Restore
@@ -2169,7 +2169,8 @@ if (!triggered)
        
        
         
-         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.
         
        
        
@@ -2542,7 +2543,8 @@ LOG:  database system is ready to accept read only connections
     Running DROP DATABASE, ALTER DATABASE ... SET TABLESPACE,
     or 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 max_standby_delay has been reached.
+    forcibly disconnected. This action occurs immediately, whatever the setting of
+   max_standby_delay.