public inbox for [email protected]  

help / color / mirror / Atom feed

From: Laurenz Albe <[email protected]>
To: David G. Johnston <[email protected]>
To: Bruce Momjian <[email protected]>
Cc: PostgreSQL-development <[email protected]>
Subject: Re: PG 18 release notes draft committed
Date: Tue, 13 May 2025 08:05:24 +0200
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAKFQuwbFa0deDEkWjomN_5FwoOdOD9UL==Px7r6UHfW5FY-gxw@mail.gmail.com>
References: <[email protected]>
	<CAKFQuwbFa0deDEkWjomN_5FwoOdOD9UL==Px7r6UHfW5FY-gxw@mail.gmail.com>

On Mon, 2025-05-12 at 20:27 -0700, David G. Johnston wrote:
> On Thursday, May 1, 2025, Bruce Momjian <[email protected]> wrote:
> > I will continue improving it until beta 1, and until the final release. 
> > I will probably add markup in 1-3 weeks.  Let the feedback begin.  ;-)
> > 
> Should all columns removed from system views and/or catalogs be listed in
> “Migration” or is there some filtering criteria? There are at minimum quite
> a few statistics related ones we’ve dropped that only appear in the Changes
> section (e.g., pg_stat_io, pg_stat_wal).

I am not sure.

On the one hand, the catalogs don't promise to be a stable API, so there
would be no need to enumerate such changes as compatibility breaks.
The "Migration" section also doesn't list changes to the exported
PostgreSQL functins, which has bitten me as extension developer several
times.

On the other hand, the catalogs are described in the documentation, which
gives them more exposure, and it doesn't seem unreasonable to document
breaking changes as well.

Do you have an idea how many changes there are?  If there are not too many,
and somebody is willing to do the work, I wouldn't be against it.

Yours,
Laurenz Albe

view thread (147+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected]
  Subject: Re: PG 18 release notes draft committed
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox