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/
