From: Zsolt Parragi <zsolt.parragi@percona.com>
In-Reply-To: <ah9VKGwwlgqF-hi7@nathan>
References: <ahm_4eOKkkKJ3Gds@nathan> <1689313.1780074543@sss.pgh.pa.us>
 <ahna7lre-xAn7DIS@nathan> <ah9VKGwwlgqF-hi7@nathan>
MIME-Version: 1.0
Date: Wed, 3 Jun 2026 07:14:53 -0700
Message-ID: 
 <CAN4CZFP5HL9Gf_-AnFN+w7MbMCNNnzN=3u-_+rk-G-JUiEzLZA@mail.gmail.com>
Subject: Re: alert clients when prepared statements are deallocated
To: pgsql-hackers@lists.postgresql.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: 
 <https://www.postgresql.org/message-id/CAN4CZFP5HL9Gf_-AnFN%2Bw7MbMCNNnzN%3D3u-_%2Brk-G-JUiEzLZA%40mail.gmail.com>
Precedence: bulk

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?