On Sat, Oct 31, 2026 at 11:24:33PM -0400, shihao zhong wrote:
> Hi Bruce,
>
> One more item for the migration section. After the BUG #19749 fix
> (18740523a), older btree indexes on character columns must be rebuilt.
> The same goes for oidvector. pg_upgrade does not do it. Until then,
> index-only scans can return wrong values.
>
> The attached patch adds a short entry that tells people to REINDEX them
> after upgrading. It is for REL_19_STABLE only. Would you add it?
>
> The fix was also back-patched to 14 through 18 (882fd416d6e on 18).
> The next minor release notes for those branches need the same REINDEX
> advice for character indexes. oidvector keeps deduplication there, so
> only 19 needs it.
I had to think about this one, particularly because PG 19 RC2 is coming
out at the same time as the minor releases, and PG 19 is coming out soon
after.
Users who are going to PG 19 are required to read all minor release
notes before moving to PG 19 and that includes the release notes we are
putting out next week; I outlined the process here:
https://momjian.us/main/blogs/pgblog/2022.html#June_13_2022
The general issue is that PG 19 is assumed to include all changes in all
the minor releases so far. Therefore, I don't think this belongs in the
PG 19 major release notes.
--
Bruce Momjian <[email protected]> https://momjian.us
EDB https://enterprisedb.com
Do not let urgent matters crowd out time for investment in the future.
