summaryrefslogtreecommitdiff
path: root/doc/src
diff options
context:
space:
mode:
authorSimon Riggs2010-10-05 23:19:05 +0000
committerSimon Riggs2010-10-05 23:19:05 +0000
commitbdf45797abe53a9e2bebd54e5475591e468a0ad1 (patch)
treefd0bb697a45684d829f102d7011f2e1acb25afd6 /doc/src
parentd79a1a138e5dc9bc190b907e754268e819678a2a (diff)
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
Diffstat (limited to 'doc/src')
-rw-r--r--doc/src/sgml/high-availability.sgml9
1 files changed, 6 insertions, 3 deletions
diff --git a/doc/src/sgml/high-availability.sgml b/doc/src/sgml/high-availability.sgml
index 211cc25d82e..9b4fa3a6d20 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>