Re: alert clients when prepared statements are deallocated

From: Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com>
To: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: alert clients when prepared statements are deallocated
Date: 2026-06-03 14:14:53
Message-ID: CAN4CZFP5HL9Gf_-AnFN+w7MbMCNNnzN=3u-_+rk-G-JUiEzLZA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: 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?

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Zsolt Parragi 2026-06-03 14:36:53 Re: Fix bug of CHECK constraint enforceability recursion
Previous Message Zsolt Parragi 2026-06-03 13:58:51 Re: Proposal: Conflict log history table for Logical Replication