"a REINDEX operation on an index pg_upgrade'd from a previous release could potentially fail." - Mailing list pgsql-admin

From Ron Johnson
Subject "a REINDEX operation on an index pg_upgrade'd from a previous release could potentially fail."
Date
Msg-id CANzqJaCk3sN+i9fs=-e_GZtn-wM=+oZU1bb4rpt0KZb31uha=Q@mail.gmail.com
Whole thread Raw
List pgsql-admin
"
In new btree indexes, the maximum index entry length is reduced by eight bytes, to improve handling of duplicate entries (Peter Geoghegan) §

This means that a REINDEX operation on an index pg_upgrade'd from a previous release could potentially fail.
"

Would a REINDEX CONCURRENTLY mitigate that risk, since https://www.postgresql.org/docs/14/sql-reindex.html#SQL-REINDEX-CONCURRENTLY says "6. The old indexes are dropped"?

--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!

pgsql-admin by date:

Previous
From: Tom Lane
Date:
Subject: Re: Why might it take so long to start up a cleanly-stopped instance?
Next
From: "M.Yousaf Maqsood"
Date:
Subject: pg_upgrade utility with --link option