Re: abi-compliance-check failure due to recent changes to pg_{clear,restore}_{attribute,relation}_stats() - Mailing list pgsql-hackers

From Nathan Bossart
Subject Re: abi-compliance-check failure due to recent changes to pg_{clear,restore}_{attribute,relation}_stats()
Date
Msg-id aQTDIO2xjmFKK0QV@nathan
Whole thread Raw
In response to Re: abi-compliance-check failure due to recent changes to pg_{clear,restore}_{attribute,relation}_stats()  (Peter Eisentraut <peter@eisentraut.org>)
Responses Re: abi-compliance-check failure due to recent changes to pg_{clear,restore}_{attribute,relation}_stats()
List pgsql-hackers
On Fri, Oct 31, 2025 at 12:02:10PM +0100, Peter Eisentraut wrote:
> What is the reason that this file is supposed to contain the history of
> relevant changes, rather than just the last one?
> 
> If you want the history, you could look at the git log of the file itself,
> no?

I think either way would ultimately be fine.  I might argue that keeping
the full history in a file with detailed explanations is more accessible
than requiring folks to run

    git log .abi-compliance-history

(Plus, if someone doesn't bother to put details in the commit message, you
then have to sleuth further to figure out what changed.)

-- 
nathan



pgsql-hackers by date:

Previous
From: "Daniel Verite"
Date:
Subject: Re: Remaining dependency on setlocale()
Next
From: Karina Litskevich
Date:
Subject: Re: doc: Improve description of io_combine_limit and io_max_combine_limit GUCs