Commitbdf4579

committed

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

Actual behaviour did not match documented behaviour and we have agreedthat it should be the docs that change.Spotted by Bernd Helmle

1 parentd79a1a1 commitbdf4579Copy full SHA for bdf4579

File tree

-3

lines changed

-3

lines changed

Lines changed: 6 additions & 3 deletions

Original file line number	Diff line number	Diff line change
`@@ -1764,12 +1764,15 @@ LOG: database system is ready to accept read only connections`
`1764`	`1764`	`</para>`
`1765`	`1765`
`1766`	`1766`	`<para>`
`1767`		`- Running <command>DROP DATABASE</>, <command>ALTER DATABASE ... SET`
`1768`		`- TABLESPACE</>, or <command>ALTER DATABASE ... RENAME</> on the primary`
	`1767`	`+ Running <command>DROP DATABASE</> or <command>ALTER DATABASE ... SET`
	`1768`	`+ TABLESPACE</> on the primary`
`1769`	`1769`	`will generate a WAL entry that will cause all users connected to that`
`1770`	`1770`	`database on the standby to be forcibly disconnected. This action occurs`
`1771`	`1771`	`immediately, whatever the setting of`
`1772`		`- <varname>max_standby_streaming_delay</>.`
	`1772`	`+ <varname>max_standby_streaming_delay</>. Note that`
	`1773`	`+ <command>ALTER DATABASE ... RENAME</> does not disconnect users, which`
	`1774`	`+ in most cases will go unnoticed, though might in some cases cause a`
	`1775`	`+ program confusion if it depends in some way upon database name.`
`1773`	`1776`	`</para>`
`1774`	`1777`
`1775`	`1778`	`<para>`

Comments

(0)