| From: | shihao zhong <zhong950419(at)gmail(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | 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-01 03:24:33 |
| Message-ID: | CAGRkXqSC-=b3oJz_0X3ao=kJG-RVFyW8aMiAq6ONs6uUSusVpA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
Thanks,
Shihao
| Attachment | Content-Type | Size |
|---|---|---|
| nocfbot-v1-0001-doc-bpchar-upgrade-note.patch | application/octet-stream | 2.5 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Manu | 2026-11-01 03:48:21 | Re: O(N^3) planning time in choose_plan_name() since 8c49a484e8e |
| Previous Message | Ayoub Kazar | 2026-11-01 02:31:18 | Re: O(N^3) planning time in choose_plan_name() since 8c49a484e8e |