diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2019-01-25 21:14:31 -0500 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2019-01-25 21:14:31 -0500 |
| commit | e8ec19cd13a5794ed8a9cd2fb187bcbfc48811d8 (patch) | |
| tree | 086fc1a0ccdf16783d218d6689c4df47f6b14830 /doc/src | |
| parent | 5b5cb3b0eb31e300ac4eaf616a6f83431531d57b (diff) | |
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
Diffstat (limited to 'doc/src')
| -rw-r--r-- | doc/src/sgml/high-availability.sgml | 11 |
1 files changed, 8 insertions, 3 deletions
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 - <command>LOAD</> </para> </listitem> + <listitem> + <para> + <command>UNLISTEN</command> + </para> + </listitem> </itemizedlist> </para> @@ -1857,7 +1862,7 @@ if (!triggered) </listitem> <listitem> <para> - <command>LISTEN</>, <command>UNLISTEN</>, <command>NOTIFY</> + <command>LISTEN</>, <command>NOTIFY</> </para> </listitem> </itemizedlist> @@ -1865,8 +1870,8 @@ if (!triggered) <para> In normal operation, <quote>read-only</> transactions are allowed to - use <command>LISTEN</>, <command>UNLISTEN</>, and - <command>NOTIFY</>, so Hot Standby sessions operate under slightly tighter + use <command>LISTEN</command> and <command>NOTIFY</command>, + 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. </para> |