Bruce Momjian <bruce@momjian.us> writes:
> thomas wrote:
>> 2008-07-05 02:16:15 CEST 6644 486ebab4.19f4 127.0.0.1(1616)ERROR: invalid
>> byte sequence for encoding "UTF8": 0xc474
> I am unclear what would cause this.
An encoding violation in an incoming SQL command would cause it, because
we won't have set debug_query_string yet. And there is no easy fix for
that, because we certainly don't want to have illegally encoded data
inside the backend. The best possible scenario would be that you get
a different error while trying to translate the string back out for the
client, and the worst would be one of those recursive encoding-error-
during-error-reporting crashes.
I think the short answer is that the OP needs to fix his client code to
not generate queries that are illegally encoded according to what he has
set client_encoding to be.
regards, tom lane
