| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: PG 18 release notes draft committed |
| Date: | 2025-05-13 06:05:24 |
| Message-ID: | 35e7cab7148bb4d1489f61fadc16d3f6cf3d9be9.camel@cybertec.at |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, 2025-05-12 at 20:27 -0700, David G. Johnston wrote:
> On Thursday, May 1, 2025, Bruce Momjian <bruce(at)momjian(dot)us> 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dilip Kumar | 2025-05-13 06:22:47 | Re: make VALIDATE domain constraint lock on related relations as ShareUpdateExclusiveLock |
| Previous Message | Dilip Kumar | 2025-05-13 05:56:52 | Re: Suggestion to add --continue-client-on-abort option to pgbench |