aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2019-01-25 21:14:31 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2019-01-25 21:14:49 -0500
commitebfe20dc706bd3238a9bdf3b44cd8f82337e86a8 (patch)
tree0e68e06941f1b17d5e617d1fb9132f99830509bf
parentc9b75c5838feeae73dbae00bce9d8f650b80ba38 (diff)
downloadpostgresql-ebfe20dc706bd3238a9bdf3b44cd8f82337e86a8.tar.gz
postgresql-ebfe20dc706bd3238a9bdf3b44cd8f82337e86a8.zip
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
-rw-r--r--doc/src/sgml/high-availability.sgml11
-rw-r--r--src/backend/tcop/utility.c2
-rw-r--r--src/test/regress/expected/hs_standby_allowed.out3
-rw-r--r--src/test/regress/expected/hs_standby_disallowed.out4
-rw-r--r--src/test/regress/sql/hs_standby_allowed.sql4
-rw-r--r--src/test/regress/sql/hs_standby_disallowed.sql2
6 files changed, 16 insertions, 10 deletions
diff --git a/doc/src/sgml/high-availability.sgml b/doc/src/sgml/high-availability.sgml
index 4882b20828a..bbab7395a21 100644
--- a/doc/src/sgml/high-availability.sgml
+++ b/doc/src/sgml/high-availability.sgml
@@ -1767,6 +1767,11 @@ if (!triggered)
Plugins and extensions - <command>LOAD</command>
</para>
</listitem>
+ <listitem>
+ <para>
+ <command>UNLISTEN</command>
+ </para>
+ </listitem>
</itemizedlist>
</para>
@@ -1856,7 +1861,7 @@ if (!triggered)
</listitem>
<listitem>
<para>
- <command>LISTEN</command>, <command>UNLISTEN</command>, <command>NOTIFY</command>
+ <command>LISTEN</command>, <command>NOTIFY</command>
</para>
</listitem>
</itemizedlist>
@@ -1864,8 +1869,8 @@ if (!triggered)
<para>
In normal operation, <quote>read-only</quote> transactions are allowed to
- use <command>LISTEN</command>, <command>UNLISTEN</command>, and
- <command>NOTIFY</command>, 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>
diff --git a/src/backend/tcop/utility.c b/src/backend/tcop/utility.c
index 27ae6be7517..6ec795f1b46 100644
--- a/src/backend/tcop/utility.c
+++ b/src/backend/tcop/utility.c
@@ -629,7 +629,7 @@ standard_ProcessUtility(PlannedStmt *pstmt,
{
UnlistenStmt *stmt = (UnlistenStmt *) parsetree;
- PreventCommandDuringRecovery("UNLISTEN");
+ /* we allow UNLISTEN during recovery, as it's a noop */
CheckRestrictedOperation("UNLISTEN");
if (stmt->conditionname)
Async_Unlisten(stmt->conditionname);
diff --git a/src/test/regress/expected/hs_standby_allowed.out b/src/test/regress/expected/hs_standby_allowed.out
index 526f88f2bec..00b8faf9eb6 100644
--- a/src/test/regress/expected/hs_standby_allowed.out
+++ b/src/test/regress/expected/hs_standby_allowed.out
@@ -208,6 +208,9 @@ LOCK hs1 IN ACCESS SHARE MODE;
LOCK hs1 IN ROW SHARE MODE;
LOCK hs1 IN ROW EXCLUSIVE MODE;
COMMIT;
+-- UNLISTEN
+UNLISTEN a;
+UNLISTEN *;
-- LOAD
-- should work, easier if there is no test for that...
-- ALLOWED COMMANDS
diff --git a/src/test/regress/expected/hs_standby_disallowed.out b/src/test/regress/expected/hs_standby_disallowed.out
index bc117413ffd..dff0953e9a6 100644
--- a/src/test/regress/expected/hs_standby_disallowed.out
+++ b/src/test/regress/expected/hs_standby_disallowed.out
@@ -118,10 +118,6 @@ listen a;
ERROR: cannot execute LISTEN during recovery
notify a;
ERROR: cannot execute NOTIFY during recovery
-unlisten a;
-ERROR: cannot execute UNLISTEN during recovery
-unlisten *;
-ERROR: cannot execute UNLISTEN during recovery
-- disallowed commands
ANALYZE hs1;
ERROR: cannot execute ANALYZE during recovery
diff --git a/src/test/regress/sql/hs_standby_allowed.sql b/src/test/regress/sql/hs_standby_allowed.sql
index a33199dbbdf..6debddc5e99 100644
--- a/src/test/regress/sql/hs_standby_allowed.sql
+++ b/src/test/regress/sql/hs_standby_allowed.sql
@@ -110,6 +110,10 @@ LOCK hs1 IN ROW SHARE MODE;
LOCK hs1 IN ROW EXCLUSIVE MODE;
COMMIT;
+-- UNLISTEN
+UNLISTEN a;
+UNLISTEN *;
+
-- LOAD
-- should work, easier if there is no test for that...
diff --git a/src/test/regress/sql/hs_standby_disallowed.sql b/src/test/regress/sql/hs_standby_disallowed.sql
index 21bbf526b74..a470600eec8 100644
--- a/src/test/regress/sql/hs_standby_disallowed.sql
+++ b/src/test/regress/sql/hs_standby_disallowed.sql
@@ -88,8 +88,6 @@ COMMIT;
-- Listen
listen a;
notify a;
-unlisten a;
-unlisten *;
-- disallowed commands