-
- Downloads
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
Showing
- doc/src/sgml/high-availability.sgml 8 additions, 3 deletionsdoc/src/sgml/high-availability.sgml
- src/backend/tcop/utility.c 1 addition, 1 deletionsrc/backend/tcop/utility.c
- src/test/regress/expected/hs_standby_allowed.out 3 additions, 0 deletionssrc/test/regress/expected/hs_standby_allowed.out
- src/test/regress/expected/hs_standby_disallowed.out 0 additions, 4 deletionssrc/test/regress/expected/hs_standby_disallowed.out
- src/test/regress/sql/hs_standby_allowed.sql 4 additions, 0 deletionssrc/test/regress/sql/hs_standby_allowed.sql
- src/test/regress/sql/hs_standby_disallowed.sql 0 additions, 2 deletionssrc/test/regress/sql/hs_standby_disallowed.sql
Loading
Please register or sign in to comment