Feedback-ID: ie0a040ee:Fastmail
Message-ID: <10e5526f-364c-4867-b6f7-91f13a9494e4@eisentraut.org>
Date: Thu, 12 Feb 2026 13:02:12 +0100
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: pgsql: Add file_extend_method=posix_fallocate,write_zeros.
To: Michael Paquier <michael@paquier.xyz>,
 Thomas Munro <tmunro@postgresql.org>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
References: <E1voE6M-001P1f-18@gemulon.postgresql.org>
 <aYXQ3VhPEqkTi0dZ@paquier.xyz>
Content-Language: en-US
From: Peter Eisentraut <peter@eisentraut.org>
In-Reply-To: <aYXQ3VhPEqkTi0dZ@paquier.xyz>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: 
 <https://www.postgresql.org/message-id/10e5526f-364c-4867-b6f7-91f13a9494e4%40eisentraut.org>
Precedence: bulk

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.