On Tue, Mar 29, 2016 at 7:31 PM, Tom Lane <t...@sss.pgh.pa.us> wrote: > A corrupt index could easily fail to detect uniqueness violations (because > searches fail to find entries they should find). Not sure I believe that > it would make false reports of a uniqueness conflict that's not really > there.
Sure. But looking at how texteq() is implemented, it certainly seems impossible that that could happen. Must have been a miscommunication somewhere. I'll fix it. Do you think it would be okay if the SQL query to detect potentially affected indexes only considered the leading attribute? Since that's the only attribute that could use abbreviated keys, it ought to be safe to not require users to REINDEX indexes that happen to have a second-or-subsequent text/varchar(n) attribute that doesn't use the C locale. Maybe it's not worth worrying about. -- Peter Geoghegan -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
