postgres.git / summary / log / commit / refs
commit 898f60dd75595bc7bad3487e6489cdd9318919cd
Author: Nathan Bossart <nathan@postgresql.org>
Date: Tue Nov 17 22:36:48 2026 +0000
Add .abi-compliance-history to v19 branch.
Discussion: https://postgr.es/m/avyECLVc0DHP16I1%40nathan
Backpatch-through: 19 only
.abi-compliance-history | 26 ++++++++++++++++++++++++++
1 file changed, 26 insertions(+)
diff --git a/.abi-compliance-history b/.abi-compliance-history
new file mode 100644
index 00000000000..2e63788a64f
--- /dev/null
+++ b/.abi-compliance-history
@@ -0,0 +1,26 @@
+# Reference point for ABI compliance checks
+#
+# This file lists commits on the current branch that break ABI compatibility in
+# ways that have been deemed acceptable (e.g., removing an extern function with
+# no third-party uses). The primary intent of this file is to control the ABI
+# compliance checks on the buildfarm, but it also serves as a central location
+# to document the justification for each.
+#
+# In general, entries should be added reactively after an abi-compliance-check
+# buildfarm failure. It is important to verify the details of the breakage
+# match expectations, as the first entry listed will become the updated ABI
+# baseline point.
+#
+# Add new entries by adding the output of the following to the top of the file:
+#
+# $ git log --pretty=format:"%H%n#%n# %s%n# %cd%n#%n# <ADD JUSTIFICATION HERE>" $ABIBREAKGITHASH -1 --date=iso
+#
+# Be sure to replace "<ADD JUSTIFICATION HERE>" with details of your change and
+# why it is deemed acceptable.
+
+5c839a2a08b9b87a349be97371fac6c5a2873b10
+#
+# Stamp 19.0.
+# 2026-11-16 15:02:58 -0500
+#
+# This is the original ABI baseline point for REL_19_STABLE.
[parent: 5c839a2a08b9]