From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | jian he <jian(dot)universality(at)gmail(dot)com> |
Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: First draft of PG 17 release notes |
Date: | 2024-05-16 02:53:48 |
Message-ID: | CAKFQuwZHK2g8bvr3feRSbS3LWWRSyct-EbVfaKnykaJhPoxJXw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wednesday, May 15, 2024, jian he <jian(dot)universality(at)gmail(dot)com> wrote:
> On Thu, May 9, 2024 at 12:04 PM Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> >
> > I have committed the first draft of the PG 17 release notes; you can
> > see the results here:
> >
> > https://momjian.us/pgsql_docs/release-17.html
> >
>
> in section: E.1.2. Migration to Version 17
>
> >> Rename I/O block read/write timing statistics columns of
> pg_stat_statement (Nazir Bilal Yavuz)
> >> This renames "blk_read_time" to "shared_blk_read_time", and
> "blk_write_time" to "shared_blk_write_time".
>
> we only mentioned, pg_stat_statements some columns name changed
> in "E.1.2. Migration to Version 17"
> but if you look at the release note pg_stat_statements section,
> we added a bunch of columns, which are far more incompatibile than
> just colunm name changes.
>
> not sure we need add these in section "E.1.2. Migration to Version 17"
>
>
New columns are not a migration issue since nothing being migrated forward
ever referenced them. Its the ones that existing code knows about that
we’ve removed (including renames) that matter from a migration perspective.
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2024-05-16 02:55:47 | Re: First draft of PG 17 release notes |
Previous Message | Bruce Momjian | 2024-05-16 02:48:27 | Re: First draft of PG 17 release notes |