mirrors/postgres
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

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

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

Spotted by Bernd Helmle
This commit is contained in:
Simon Riggs 2010-10-06 00:19:05 +01:00
parent d79a1a138e
commit bdf45797ab
1 changed files with 6 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
doc/src/sgml/high-availability.sgml
View File

@ -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>