To answer my own mail, I shut down the 8.1 database, and started up the
8.0 PostgreSQL install that is still on my computer, and the backups
work fine. I do get the message about how 8.1 handles sorting of unicode
characters more correctly, but looking at my backups, I can see that the
full back up failed about the time that I switched to the newer version.
Is there a fix for this? Is this a bug? Is there a workaround?
Thanks for any help.
JP
JP Glutting wrote:
I have seen several people with this same error. I get mine when
trying to backup using pg_dump, causing my backups to fail.
I am using PostgreSQL 8.1 on Windows XP.The databases are in UTF8. I
get the same error from the command line and using pgadmin3.
Has anyone found a solution for this? Looking around online, I see
that this supposedly codes for a lowercase a with a circumflex (which
I don't have in tha table thet triggeres the error), but that this may
be the first part of a three-byte sequence that codes for something else.
Does anyone know of a way to pinpoint the character in the database? I
am not sure how to search for a raw unicode character through psql or
pgadmin...
Thanks for any help!
JP
---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
--
____________________________________________________
Oficina de Qualitat Tel: 973 703 103
Universitat de Lleida Fax: 973 702 036
Pl. Víctor Siurana, 1
25003 Lleida
____________________________________________________
---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster
