database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-07-28 23:42:10 +03:00
Code Activity

Docs for behaviour change of drop database during Hot Standby

Browse Source 
Adding missing docs for previous Hot Standby patch.
This commit is contained in:
Simon Riggs
2010-01-10 16:27:27 +00:00
parent 48eaa34d44
commit f537e7dfa4
1 changed files with 5 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
doc/src/sgml/backup.sgml
View File

@ -1,4 +1,4 @@
<!-- $PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.133 2009/12/20 03:49:58 rhaas Exp $ -->
<!-- $PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.134 2010/01/10 16:27:27 sriggs Exp $ -->
<chapter id="backup">
<title>Backup and Restore</title>
@ -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>