Evan Carroll <me@evancarroll.com> writes:
> BTW, The database version is 9.1.3. I'll try and work on a test that
> generates this same error, not exactly sure why it is getting
> generated though.
Also see whether you can reproduce the error in a fresh database.
I continue to think the problem is an incorrect collation value in
some system catalog entry; if that's it, nobody will be able to
reproduce it. You might try checking to see that there are no
un-updated rows matching those fixup queries.
regards, tom lane
