| From: | Rob Sargent <robjsargent(at)gmail(dot)com> |
|---|---|
| To: | gnanam(at)zoniac(dot)com |
| Cc: | pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: Invalid message format Exception |
| Date: | 2010-05-13 15:18:03 |
| Message-ID: | 4BEC182B.6010200@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc pgsql-sql |
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hernan Danielan | 2010-05-14 15:09:21 | Socket close exception |
| Previous Message | Gnanakumar | 2010-05-13 07:04:19 | Re: Invalid message format Exception |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Trinath Somanchi | 2010-05-14 08:42:17 | Postgresql database |
| Previous Message | Justin Graf | 2010-05-13 13:57:56 | Re: best paging strategies for large datasets? |