Comment 1 for bug 650777

Is it possible to have a an example reproducing the problem?

The failing comparison reported in the error message is one performed by postgres, not by python, and it shouldn't be anything concerning unicode strings. I think it is related to a change committed before Psycopg 2.2.0 where the binary adapter started adding a ::bytea to disambiguate the type and make it work where the context is not explicit, e.g. in function calls or in arrays.

Psycopg has now a bug tracker again: http://psycopg.lighthouseapp.com/