From: Tom Lane <tgl@sss.pgh.pa.us>
To: Randall Wilson <rwilson@earthcomber.com>
Cc: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: Idle Error invalid byte sequence
Date: Thu, 18 Sep 2008 16:57:30 -0400
Message-ID: <2079.1221771450@sss.pgh.pa.us> (raw)
In-Reply-To: <48D2B5B0.9020708@earthcomber.com>
References: <48D273D8.7010603@earthcomber.com>
<23674.1221761835@sss.pgh.pa.us>
<48D2B5B0.9020708@earthcomber.com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, rwilson@earthcomber.com
Subject: Re: Idle Error invalid byte sequence
In-Reply-To: <2079.1221771450@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox