Right after upgrading our postgres servers from 11.15 to 11.17 we started to encounter problems with data. Namely, when the query hit the index, it returned a single row; when the query hit a relation directly, it returned more than one row. Attempt to REINDEX revealed the underlying data had duplicates (unique index reindexing failed).
Version facts: we started out with 11.12 jan 2022 upgraded to 11.14 mar 2022 to 11.15 oct 2022 to 11.17
The bottom line is we would like to understand if the index corruption and its manifestation is explained by the above release fixes or is there something else that should be investigated further here with the help from the community.
What if you construct a select statement containing the row id and the column which has the problematic index into a new table. Then perform queries on this table to test for uniqueness of the column on which the problematic index was reported.
