From: Rob Sargent <robjsargent@gmail.com>
To: gnanam@zoniac.com
Cc: pgsql-sql@postgresql.org
Subject: Re: Invalid message format Exception
Date: Thu, 13 May 2010 09:18:03 -0600
Message-ID: <4BEC182B.6010200@gmail.com> (raw)
In-Reply-To: <00ff01caf26a$8654f3d0$92fedb70$@com>
References: <00da01caf04b$c182f900$4488eb00$@com>
<016a01caf1be$be59d900$3b0d8b00$@com>
<00ff01caf26a$8654f3d0$92fedb70$@com>
On 05/13/2010 01:04 AM, Gnanakumar wrote:
> Hi Rob,
>
>> I'm sure most will urge you to move to UTF-8 encoding asap.
> Did you mean the database encoding to changed from SQL_ASCII to UTF-8?
>
Yes. That's pretty much the standard now. I think it's Postgres'
default installation now (but don't quote me on that).
>> Have you tracked down the "offending" insert statement? Perhaps it's a
>> trigger trying to generate a log message?
> No, I don't have any trigger on this table for INS/UPD/DEL.
>
I think you'll need to track down example of inserts which are causing
the problem.
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-sql@postgresql.org
Cc: robjsargent@gmail.com, gnanam@zoniac.com
Subject: Re: Invalid message format Exception
In-Reply-To: <4BEC182B.6010200@gmail.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