| From: | Álvaro Herrera <alvherre(at)kurilemu(dot)de> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | shihao zhong <zhong950419(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, PostgreSQL-development <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: First draft of PG 19 release notes |
| Date: | 2026-11-08 16:28:06 |
| Message-ID: | avChqb5P1jHEtnzx@alvherre.pgsql |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2026-Nov-07, Bruce Momjian wrote:
> Imagine someone is running 18.10, and they want to upgrade to 19.7.
> They will read all the release notes from 18.11 to 19.7, and it will
> tell them to reindex twice.
Well, if they use https://why-upgrade.depesz.com they won't. For
instance,
https://why-upgrade.depesz.com/show?from=16.14&to=18.6&keywords=
this will show going from 16.4 to 17, then to 17.1, 17.2 [etc] until
17.6, and then it says to jump to 18. So the release notes from 17.7
and up are not included, presumably because Depesz knows that these are
duplicates.
I don't think we _have_ to change the way our release notes are
structured in order to cope with this. It may be nice to have a
way to present them that matches what Depesz's page does, though.
Or at least an explanation about how it would go.
--
Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sho Ito | 2026-11-08 17:15:03 | Re: psql: Don't offer partitioned tables after CREATE INDEX CONCURRENTLY |
| Previous Message | Tom Lane | 2026-11-08 16:06:40 | Re: Draft back-branch release notes are up |