On Wednesday 25 April 2007 06:29, Francois Deliege <fdeliege@cs.aau.dk>
wrote:
> ERROR: invalid byte sequence for encoding "UTF8": 0x92
> HINT: This error can also happen if the byte sequence does not match
> the encoding expected by the server, which is controlled by
> "client_encoding".
Newer versions of PostgreSQL do much stricter checks of UTF-8 data than
older versions did. It is very possible that if you are upgrading
versions that your original data is invalid UTF-8 even if it's in a
UTF-8 database.
And of course, if the source database is SQL-ASCII, then any sort of
invalid data error is possible when importing to a UTF-8 database.
iconv is usually suggested as the tool to correct encoding errors in the
dump file prior to importing to a new database. There are several
threads in the archives that address this issue.
--
"It is a besetting vice of democracies to substitute public opinion for
law." - James Fenimore Cooper