Re: Idle Error invalid byte sequence - Mailing list pgsql-admin

From Randall Wilson
Subject Re: Idle Error invalid byte sequence
Date
Msg-id 48D2CCF4.9090007@earthcomber.com
Whole thread Raw
In response to Re: Idle Error invalid byte sequence  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Idle Error invalid byte sequence  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-admin
log_line_prefix = '[%t] %i'
So, "idle" is just the "command tag", which probably means it's not
associated with a command.

Unless you think grepping my plain text backup is a waste of time,
you've answered all my questions (Thanks) and I don't need a reply.
Thanks again,
Randy Wilson

Tom Lane wrote:
> Randall Wilson <rwilson@earthcomber.com> writes:
>
>> Yes, the encoding was changed from SQL_ASCII to UTF-8. Does the fact
>> that it's an "Idle" error conform your theory that some client is
>> causing the error? I thought the "Idle" error was caused by errors found
>> during background processes, like vacuums.
>>
>
> You'd have to tell us what your log_line_prefix is before we could
> interpret that, but yeah, an encoding error in an incoming query string
> would be reported before the backend could even consider going non-idle.
>
> A SQL_ASCII database would have accepted any data whatsoever.  If you
> want to change to something where you actually know the encoding, that's
> fine, but realize that you're going to have to make your clients be
> honest about what encoding they're using, too.
>
>             regards, tom lane
>
>

Attachment

pgsql-admin by date:

Previous
From: Tom Lane
Date:
Subject: Re: type unknown?
Next
From: Carol Walter
Date:
Subject: Re: type unknown?