Re: First draft of PG 17 release notes

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Jelte Fennema-Nio <postgres(at)jeltef(dot)nl>, Nathan Bossart <nathandbossart(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: First draft of PG 17 release notes
Date: 2024-09-17 08:19:29
Message-ID: 202409170819.mnrurm7gggrl@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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)

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jelte Fennema-Nio 2024-09-17 08:36:22 Re: Detailed release notes
Previous Message Alvaro Herrera 2024-09-17 08:12:44 Re: Detailed release notes