We see this a lot with web applications where users cut/paste from MS-Word.
In our case, the web app and db (oracle) are the same character set, so no translation or validation is done.
Oracle will store the values, even though they aren't valid UTF8 characters.
We run into problems when the values are imported to our Greenplum/postgres dw.
We don't have a workaround.
From: pgadmin-support-owner(at)postgresql(dot)org [mailto:pgadmin-support-owner(at)postgresql(dot)org] On Behalf Of Guillaume Lelarge
Sent: Wednesday, February 23, 2011 2:41 PM
To: Maximilian Tyrtania
Subject: Re: [pgadmin-support] "Invalid byte sequence" message
Le 22/02/2011 21:58, Guillaume Lelarge a écrit :
> Le 16/02/2011 14:21, Maximilian Tyrtania a écrit :
>> Just found this in my log file:
>> <postgres%2011-02-16 13:55:32 CET22021>ERROR: invalid byte sequence for encoding "UTF8": 0xe3bc64
>> <postgres%2011-02-16 13:55:32 CET22021>STATEMENT: SELECT pg_file_read('pg_log/postgresql-2011-02-16_000000.log', 100000, 50000)
>> Still not sure what's going on there. Apparently the contents of the logfile are not valid UTF8 characters. Also, after i clicked the message boxes away, the log files contents appear incomplete in the log viewer (a couple hours worth of entries are simply missing).
> I suppose it stopped to process the rest of the file once it found an
> invalid UTF8 character. There's not much we can do about this.
One guy on a french web forum has the same issue than you. Can you tell
me the value of your lc_messages parameter?
In response to
pgadmin-support by date
|Next:||From: Vik Reykja||Date: 2011-02-23 21:51:02|
|Subject: Re: "Invalid byte sequence" message|
|Previous:||From: Guillaume Lelarge||Date: 2011-02-23 20:53:34|
|Subject: Re: dynamic results of a PG_Dump or pg_Restore
in the list|