From 7887db612cefcc9f2648f3248cba1f3904c80b3b Mon Sep 17 00:00:00 2001 From: Simon Riggs Date: Wed, 6 Oct 2010 00:20:54 +0100 Subject: [PATCH] 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 --- doc/src/sgml/high-availability.sgml | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/doc/src/sgml/high-availability.sgml b/doc/src/sgml/high-availability.sgml index 16bd9d1e5b0..a4be8276be9 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 - Running DROP DATABASE, ALTER DATABASE ... SET - TABLESPACE, or ALTER DATABASE ... RENAME on the primary + Running DROP DATABASE or 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 - max_standby_streaming_delay. + max_standby_streaming_delay. Note that + 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. -- 2.39.5