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

From Guillaume Lelarge
Subject Re: "Invalid byte sequence" message
Date
Msg-id 4D6570F5.3080509@lelarge.info
Whole thread Raw
In response to Re: "Invalid byte sequence" message  (Guillaume Lelarge <guillaume@lelarge.info>)
Responses Re: "Invalid byte sequence" message  ("Little, Douglas" <DOUGLAS.LITTLE@orbitz.com>)
Re: "Invalid byte sequence" message  (Vik Reykja <vikreykja@gmail.com>)
Re: "Invalid byte sequence" message  (Maximilian Tyrtania <lists@contactking.de>)
List pgadmin-support
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,
afteri clicked the message boxes away, the log files contents appear incomplete in the log viewer (a couple hours worth
ofentries 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?


-- 
Guillaumehttp://www.postgresql.frhttp://dalibo.com


pgadmin-support by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: Bug report: Syntax Coloring
Next
From: Guillaume Lelarge
Date:
Subject: Re: Bug report: Syntax Coloring