Feedback-ID: ia2694551:Fastmail
Date: Tue, 17 Sep 2024 10:19:29 +0200
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Bruce Momjian <bruce@momjian.us>
Cc: Jelte Fennema-Nio <postgres@jeltef.nl>,
	Nathan Bossart <nathandbossart@gmail.com>, pgsql-hackers@postgresql.org
Subject: Re: First draft of PG 17 release notes
Message-ID: <202409170819.mnrurm7gggrl@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <ZuGk0krk-TIgP-dD@momjian.us>
Archived-At: 
 <https://www.postgresql.org/message-id/202409170819.mnrurm7gggrl%40alvherre.pgsql>
Precedence: bulk

On 2024-Sep-11, Bruce Momjian wrote:

> An interesting idea would be to report all function signature changes
> in each major release in some way.

Hmm, extension authors are going to realize this as soon as they try to
compile, so it doesn't seem necessary.  Having useful APIs _added_ is a
different matter, because those might help them realize that they can
remove parts (or #ifdef-out for newer PG versions) of their code, or add
new features; there's no Clippit saying "it looks like you're compiling
for Postgres 18, would you like to ...?".

-- 
Álvaro Herrera        Breisgau, Deutschland  —  https://www.EnterpriseDB.com/
"The important things in the world are problems with society that we don't
understand at all. The machines will become more complicated but they won't
be more complicated than the societies that run them."    (Freeman Dyson)