Re: Invalid sequence for encoding UTF8 0xe86974 - Mailing list pgsql-docs

From Holec, JPH Software
Subject Re: Invalid sequence for encoding UTF8 0xe86974
Date
Msg-id !&!AAAAAAAAAAAYAAAAAAAAAE8q5Jcv4mJImRanr8cGRrPCgAAAEAAAAIYTVJUtwwBLowxWJJoMXvEBAAAAAA==@jphsw.cz
Whole thread Raw
In response to Re: Invalid sequence for encoding UTF8 0xe86974  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
List 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.Grittner@wicourts.gov]
Sent: Tuesday, February 28, 2012 6:32 PM
To: JPH Software Holec; pgsql-docs@postgresql.org
Subject: Re: [DOCS] Invalid sequence for encoding UTF8 0xe86974

"Holec, JPH Software" <holec@jphsw.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


pgsql-docs by date:

Previous
From: "Kevin Grittner"
Date:
Subject: Re: Invalid sequence for encoding UTF8 0xe86974
Next
From: Marti Raudsepp
Date:
Subject: Update documentation wrt visibility map/index-only scans