From 3c3b34bbee41e8bb1f71e4360d444daa50ea86b1 Mon Sep 17 00:00:00 2001 From: Thomas Munro Date: Sat, 7 Feb 2026 10:56:04 +1300 Subject: [PATCH] Placate ABI checker. It's not really an ABI break if you change the layout/size of an object with incomplete type, as commit f94e9141 did, so advance the ABI compliance reference commit in 16-18 to satisfy build farm animal crake. Backpatch-through: 16-18 Discussion: https://www.postgresql.org/message-id/1871492.1770409863%40sss.pgh.pa.us --- .abi-compliance-history | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/.abi-compliance-history b/.abi-compliance-history index f4e27cfb160..58c0b0de296 100644 --- a/.abi-compliance-history +++ b/.abi-compliance-history @@ -18,6 +18,16 @@ # Be sure to replace "" with details of your change and # why it is deemed acceptable. +33e3de6d77e87d6c3c6f8f878dd8de42d37c3b8f +# +# Add file_extend_method=posix_fallocate,write_zeros. +# 2026-02-06 17:38:39 +1300 +# +# Modifying GUC tables isn't really an ABI break: the relevant object has +# incomplete type so its layout is unknown to other C translation units. +# +# Discussion: https://www.postgresql.org/message-id/flat/e1f0cd3b-0164-45f5-9705-e922e59df90f%40dunslane.net#8a350b54012c0042f9869d288e978cfe + 492a69e1407029f8c673484f44aa719a63323d77 # # Reject ADD CONSTRAINT NOT NULL if name mismatches existing constraint