Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Commit f537e7d

Browse files
Docs for behaviour change of drop database during Hot Standby
Adding missing docs for previous Hot Standby patch.
1 parent 48eaa34 commit f537e7d

File tree

1 file changed

+5
-3
lines changed

1 file changed

+5
-3
lines changed

doc/src/sgml/backup.sgml

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
<!-- $PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.133 2009/12/20 03:49:58 rhaas Exp $ -->
1+
<!-- $PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.134 2010/01/10 16:27:27 sriggs Exp $ -->
22

33
<chapter id="backup">
44
<title>Backup and Restore</title>
@@ -2169,7 +2169,8 @@ if (!triggered)
21692169
</listitem>
21702170
<listitem>
21712171
<para>
2172-
Dropping databases on the primary while that role is connected on standby.
2172+
Dropping databases on the primary while users are connected to that
2173+
database on the standby.
21732174
</para>
21742175
</listitem>
21752176
<listitem>
@@ -2542,7 +2543,8 @@ LOG: database system is ready to accept read only connections
25422543
Running <command>DROP DATABASE</>, <command>ALTER DATABASE ... SET TABLESPACE</>,
25432544
or <command>ALTER DATABASE ... RENAME</> on primary will generate a log message
25442545
that will cause all users connected to that database on the standby to be
2545-
forcibly disconnected, once <varname>max_standby_delay</> has been reached.
2546+
forcibly disconnected. This action occurs immediately, whatever the setting of
2547+
<varname>max_standby_delay</>.
25462548
</para>
25472549

25482550
<para>

0 commit comments

Comments
 (0)