Corrupt indexes in PG12, how do I fix?

That could be. I think that the leading % is enough, but I could be wrong.

3 Likes

Correct.

See, for example:

3 Likes

But… all settings are in lowercase, so just using lowercase in the query does not need ilike ?

6 Likes

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.

Welp, if it makes anyone feel better, I ran into this myself!

Caused by:
PG::UniqueViolation: ERROR:  could not create unique index "index_incoming_referers_on_path_and_incoming_domain_id_c_ccnew2"
DETAIL:  Key (path, incoming_domain_id)=(/_, 1169) is duplicated.

The instructions above – enter the container, start postgres, query the bad data, delete it by id… were helpful.

6 Likes