From e8ec19cd13a5794ed8a9cd2fb187bcbfc48811d8 Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Fri, 25 Jan 2019 21:14:31 -0500 Subject: Allow UNLISTEN in hot-standby mode. Since LISTEN is (still) disallowed, UNLISTEN must be a no-op in a hot-standby session, and so there's no harm in allowing it. This change allows client code to not worry about whether it's connected to a primary or standby server when performing session-state-reset type activities. (Note that DISCARD ALL, which includes UNLISTEN, was already allowed, making it inconsistent to reject UNLISTEN.) Per discussion, back-patch to all supported versions. Shay Rojansky, reviewed by Mi Tar Discussion: https://postgr.es/m/CADT4RqCf2gA_TJtPAjnGzkC3ZiexfBZiLmA-mV66e4UyuVv8bA@mail.gmail.com --- doc/src/sgml/high-availability.sgml | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) (limited to 'doc/src') diff --git a/doc/src/sgml/high-availability.sgml b/doc/src/sgml/high-availability.sgml index 23de642a0c1..528e6a9f4c4 100644 --- a/doc/src/sgml/high-availability.sgml +++ b/doc/src/sgml/high-availability.sgml @@ -1768,6 +1768,11 @@ if (!triggered) Plugins and extensions - LOAD + + + UNLISTEN + + @@ -1857,7 +1862,7 @@ if (!triggered) - LISTEN, UNLISTEN, NOTIFY + LISTEN, NOTIFY @@ -1865,8 +1870,8 @@ if (!triggered) In normal operation, read-only transactions are allowed to - use LISTEN, UNLISTEN, and - NOTIFY, so Hot Standby sessions operate under slightly tighter + use LISTEN and NOTIFY, + so Hot Standby sessions operate under slightly tighter restrictions than ordinary read-only sessions. It is possible that some of these restrictions might be loosened in a future release. -- cgit v1.2.3