From: | "Holec, JPH Software" <holec(at)jphsw(dot)cz> |
---|---|
To: | "'Kevin Grittner'" <Kevin(dot)Grittner(at)wicourts(dot)gov>, <pgsql-docs(at)postgresql(dot)org> |
Subject: | Re: Invalid sequence for encoding UTF8 0xe86974 |
Date: | 2012-02-28 18:22:37 |
Message-ID: | !&!AAAAAAAAAAAYAAAAAAAAAE8q5Jcv4mJImRanr8cGRrPCgAAAEAAAAIYTVJUtwwBLowxWJJoMXvEBAAAAAA==@jphsw.cz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
Thank you, but this is a not help for me.
Why PG gives me not valid character and do you mean read *.log file as
binary? Do you know how to solve?
Pavel
-----Original Message-----
From: Kevin Grittner [mailto:Kevin(dot)Grittner(at)wicourts(dot)gov]
Sent: Tuesday, February 28, 2012 6:32 PM
To: JPH Software Holec; pgsql-docs(at)postgresql(dot)org
Subject: Re: [DOCS] Invalid sequence for encoding UTF8 0xe86974
"Holec, JPH Software" <holec(at)jphsw(dot)cz> wrote:
> pg_read_file('pg_log... gives me this report and 0xe86974 doesn't know
> Google...
It would be an odd web page which listed all the values which are not valid
as character encodings in any particular encoding scheme.
> Can You help me?
Questions like this belong on the pgsql-general list; this one is for
discussions about documentation.
> PG 8.4.9 on Windows, database UTF8 and client also Windows... and
> except pg_read_file everything works fine...
You are trying to read a file as text, which is character based.
You are using UTF8 and the file contains data which is not a valid
UTF8 code point.
-Kevin
From | Date | Subject | |
---|---|---|---|
Next Message | Marti Raudsepp | 2012-03-03 00:16:47 | Update documentation wrt visibility map/index-only scans |
Previous Message | Kevin Grittner | 2012-02-28 17:31:30 | Re: Invalid sequence for encoding UTF8 0xe86974 |