Re: alert clients when prepared statements are deallocated - Mailing list pgsql-hackers

From Zsolt Parragi
Subject Re: alert clients when prepared statements are deallocated
Date
Msg-id CAN4CZFP5HL9Gf_-AnFN+w7MbMCNNnzN=3u-_+rk-G-JUiEzLZA@mail.gmail.com
Whole thread
In response to Re: alert clients when prepared statements are deallocated  (Nathan Bossart <nathandbossart@gmail.com>)
Responses Re: alert clients when prepared statements are deallocated
List pgsql-hackers
Hello

@@ -558,6 +584,9 @@ DropAllPreparedStatements(void)
         /* Now we can remove the hash table entry */
         hash_search(prepared_queries, entry->stmt_name, HASH_REMOVE, NULL);
     }
+
+    /* Alert the client */
+    SendStmtDeallocMsg("");
 }

DropAllPreparedStatements has an early return if prepared_queries is
uninitialized, so we don't send anything in that case - but it calls
SendStmtDeallocMsg if it is initialized even when no nothing was
removed. This seems inconsistent to me, is it intentional?



pgsql-hackers by date:

Previous
From: Zsolt Parragi
Date:
Subject: Re: Proposal: Conflict log history table for Logical Replication
Next
From: Zsolt Parragi
Date:
Subject: Re: Fix bug of CHECK constraint enforceability recursion