Thomas Kellerer <spam_eater@gmx.net> writes:
> character 0xc3b6 of encoding "UTF8" has no equivalent in "WIN1251" [SQL
> State=22P05]
Indeed, that's what the conversion table embedded in the backend
thinks. Some cursory poking about in src/backend/utils/mb/Unicode/
says that we derive these tables mechanically from authoritative data
at ftp://www.unicode.org/Public/MAPPINGS/ ... so maybe you need to
take this up with them. What's your basis for asserting that this
character exists in code page 1251?
regards, tom lane
