pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Randall Wilson <rwilson@earthcomber.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: Idle Error invalid byte sequence
Date: Thu, 18 Sep 2008 16:49:40 -0500
Message-ID: <48D2CCF4.9090007@earthcomber.com> (raw)
In-Reply-To: <2079.1221771450@sss.pgh.pa.us>
References: <48D273D8.7010603@earthcomber.com>
	<23674.1221761835@sss.pgh.pa.us>
	<48D2B5B0.9020708@earthcomber.com>
	<2079.1221771450@sss.pgh.pa.us>

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
>
>   

Attachments:

rwilson.vcf (text/x-vcard, 322B) download begin:vcard fn:Randall Wilson n:Wilson;Randall org:Earthcomber, LLC;Development adr:Suite 114;;7777 Lake St.;River Forest;IL;60305;USA email;internet:rwilson@earthcomber.com title:Senior Software Engineer tel;work:708-366-1611 tel;cell:773-620-3042 x-mozilla-html:FALSE url:http://www.earthcomber.com version:2.1 end:vcard

view thread (6+ messages)  latest in thread

Message-ID: <48D2CCF4.9090007@earthcomber.com>
Permalink:  ../48D2CCF4.9090007@earthcomber.com/
Also on:    postgresql.org/message-id/48D2CCF4.9090007@earthcomber.com

 · 

reply

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: rwilson@earthcomber.com, tgl@sss.pgh.pa.us
  Subject: Re: Idle Error invalid byte sequence
  In-Reply-To: <48D2CCF4.9090007@earthcomber.com>

* 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