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
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?
> 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 t
I'm sure most will urge you to move to UTF-8 encoding asap.
Have you tracked down the "offending" insert statement? Perhaps it's a
trigger trying to generate a log message?
On 05/12/2010 04:34 AM, Gnanakumar wrote:
> Hi,
>
> Because there was no response for this question already posted in
> pg
Hi,
Because there was no response for this question already posted in
pgsql-j...@postgresql.org mailing list, I'm posting it here.
I'm using PostgreSQL 8.2 and my production server is based on CentOS release
5.2 (Final).
JDBC Jar: postgresql-8.2-508.jdbc4.jar
I noticed from my server log that s
