Re: "Invalid byte sequence" message - Mailing list pgadmin-support

From Maximilian Tyrtania
Subject Re: "Invalid byte sequence" message
Date
Msg-id 5B58DEEA-FBE8-43D8-857E-14B961E3EDE5@contactking.de
Whole thread Raw
In response to "Invalid byte sequence" message  (Maximilian Tyrtania <lists@contactking.de>)
Responses Re: "Invalid byte sequence" message  (Guillaume Lelarge <guillaume@lelarge.info>)
List pgadmin-support
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
iclicked the message boxes away, the log files contents appear incomplete in the log viewer (a couple hours worth of
entriesare simply missing).  

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

Am 15.02.2011 um 16:07 schrieb Maximilian Tyrtania:

> Hi again,
>
> i upgraded im pg installation to 9.0.3 (from 8.4.2) and now i'm having trouble looking at my log files with pg admin
1.12.2.(on Mac OS 10.6) - on every refresh I'd get a messagebox saying: 
>
> 2011-02-15 14:28:12 ERROR  : ERROR:  invalid byte sequence for encoding "UTF8": 0xe3b66c
>
> The server runs on Mac OS 10.6, the data is UTF8, and the client connection settings are as well.
> Any pointers?


pgadmin-support by date:

Previous
From: Jakob Egger
Date:
Subject: Bug report: Syntax Coloring
Next
From: rleonanaya
Date:
Subject: Re: 1.12.1 - cannot dump from older server versions