On 06.02.26 12:30, Michael Paquier wrote:
Hi Thomas,
On Fri, Feb 06, 2026 at 05:09:54AM +0000, Thomas Munro wrote:
Add file_extend_method=posix_fallocate,write_zeros.
It looks like you need to update .abi-compliance-check for stable
branches down to v16, due to the new entry added to
ConfigureNamesEnum. See:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=crake&dt=2026-02-06%2009%3A27%3A27
I suppose technically this is an ABI change since the size of
ConfigureNamesEnum is changed, but it seems this is irrelevant in
practice. Could it be possible to ignore stuff like this without manual
intervention?
The concern is that say authors or packagers of extensions will observe
that there was an ABI change and will think they have to do some extra
work, but in practice probably not.
The goal should be to not have ABI changes in stable branches. If we
just keep marking ABI changes without distinction, then this could lead
to fatigue.
