Allow UNLISTEN in hot-standby mode.
Tom Lane <tgl@sss.pgh.pa.us>
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
Files
| Path | Change | +/− |
|---|---|---|
| doc/src/sgml/high-availability.sgml | modified | +8 −3 |
| src/backend/tcop/utility.c | modified | +1 −1 |
| src/test/regress/expected/hs_standby_allowed.out | modified | +3 −0 |
| src/test/regress/expected/hs_standby_disallowed.out | modified | +0 −4 |
| src/test/regress/sql/hs_standby_allowed.sql | modified | +4 −0 |
| src/test/regress/sql/hs_standby_disallowed.sql | modified | +0 −2 |
Documentation touched
Discussion
- [PATCH] Allow UNLISTEN during recovery 8 messages · 2018-11-18 → 2019-01-26