On Sat, Nov 7, 2026 at 07:17:02PM -0500, shihao zhong wrote: > Hi Tom and Bruce, > > Thanks Bruce for explaining how the minor release notes fit in. That > makes sense, so please drop my patch. > > Tom, thanks for pointing out that CHAR(n) is safe.
This showed me that there is _some_ confusion in the process. Suppose in PG 18.14 we tell users to reindex, and in PG 19.5, which was released on the same day as 18.14, we tell people to reindex for the same reason. 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. Obviously the _reason_ for the reindex will be the same, and they will need to realize that as part of their upgrade procedure. In fact a lot of the items that are backpatched will be duplicates. I am just not sure that we give a simple way of avoiding this confusion. -- Bruce Momjian <[email protected]> https://momjian.us EDB https://enterprisedb.com Do not let urgent matters crowd out time for investment in the future.
