What to reindex after PostgreSQL's 52-CVE batch
On 12 November PostgreSQL released 18.7, 17.12, 16.16, 15.20 and 14.25 with 52 CVEs fixed. The package and the restart close all 52, but the same batch carries five index-corruption items that do not fix themselves: GIN, pg_trgm, bpchar and TOAST-table indexes stay corrupt until you run REINDEX by hand. Inside: the right order of operations, four census queries that change nothing, the bpchar nuance that rules out CHAR(n), and why your incremental backup chain stopped being a chain.