"NTPT" <ntpt@xxxxxxxxxx> writes: > Without "set client_encoding to win1250" query works. I am curious why there > is a MULE_INTERNAL mentioned even when \l+ say that corresponding database > is created with (and even all the cluster) LATIN2 encoding. The conversions between LATIN2 and WIN1250 go by way of MULE_INTERNAL to reduce duplication of code. It shouldn't make any difference to the end result though. Are you sure that the characters you're using are supposed to have representations in both character sets? > May be a bug in charset translation routines of postgres ? If you think that, you need to provide us with the exact codes that are being mistranslated and what you think they should translate to. regards, tom lane
