Update .abi-compliance-history for pgstat_drop_entry()

As noted in the commit message of 850b9218c8e4, this function has gained
an extra called "missing_ok".  All the callers of this routine should be
in core in the v15-v17 range.  For v18, I have found one custom stats
kind that would be impacted by this change.

Discussion: https://postgr.es/m/ajOE3uRxVgSlPRcw@paquier.xyz
Backpatch-through: 15-18

diff --git a/.abi-compliance-history b/.abi-compliance-history
index a4bf3336cacbc1ebc86d19198a413b3c7172ec28..6ba3e7519b706bd2724c746c82f5bfd487218c9b 100644 (file)
--- a/.abi-compliance-history
+++ b/.abi-compliance-history
@@ -18,6 +18,15 @@
 # Be sure to replace "<ADD JUSTIFICATION HERE>" with details of your change and
 # why it is deemed acceptable.
 
+5cc59834b860ed48d710c1baa9c50c66540c64d0
+#
+# Fix PANIC with track_functions due to concurrent drop of pgstats entries
+# 2026-06-18 11:49:34 +0900
+#
+# This commit has added a "missing_ok" argument to pgstat_drop_entry().  All
+# the callers of this routine are in core for v15-v17.  One custom stats kinds
+# available in the public since v18 is impacted (maintainer informed).
+
 8d9a97e0bb6d820dac553848f0d5d8cc3f3e219d
 #
 # Avoid name collision with NOT NULL constraints