Skip site navigation (1) Skip section navigation (2)

Re: "Invalid byte sequence" message

From: Maximilian Tyrtania <lists(at)contactking(dot)de>
To: Guillaume Lelarge <guillaume(at)lelarge(dot)info>
Cc: pgadmin-support(at)postgresql(dot)org
Subject: Re: "Invalid byte sequence" message
Date: 2011-02-26 12:48:52
Message-ID: 288696C8-DBB8-409B-B23F-B8E34B134A8F@contactking.de (view raw or flat)
Thread:
Lists: pgadmin-support
Am 23.02.2011 um 21:41 schrieb Guillaume Lelarge:

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

It was set to "de_DE.UTF8". Changed it to C, which is fine with me. Seems to have fixed the problem.

Thanks,

Maximilian Tyrtania Software-Entwicklung
Dessauer Str. 6-7
10969 Berlin
http://www.contactking.de


In response to

pgadmin-support by date

Next:From: Matías ParodiDate: 2011-02-26 14:15:54
Subject: PgAdmin bug - Edit row.
Previous:From: Basil BourqueDate: 2011-02-25 01:38:15
Subject: Re: Bug - Rows in Query Output pane fail to grow in height when font size preference size is larger

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group