pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feed"UNICODE" error during restoration
4+ messages / 3 participants
[nested] [flat]
* "UNICODE" error during restoration
@ 2006-06-19 11:27 TK <kthusi@yahoo.com>
0 siblings, 0 replies; 4+ messages in thread
From: TK @ 2006-06-19 11:27 UTC (permalink / raw)
To: pgsql-admin
Hi,
We took a dump of a database running PostgreSQL 7.3.10 (on Gentoo Linux).
We tried to restore it onto a server running PostgreSQL 7.4.13 (on Gentoo Linux). This resulted in the following errors:
psql:<stdin>:13856: ERROR: invalid byte sequence for encoding "UNICODE": 0x85
....
psql:<stdin>:537916: ERROR: invalid byte sequence for encoding "UNICODE": 0xa0
...
psql:<stdin>:1009873: ERROR: invalid byte sequence for encoding "UNICODE": 0x92
...
etc.
We tried to restore the same dump on a server running PostgreSQL 7.3.9 (on Gentoo Linux) and the restoration was successful.
It also worked without any problem on a server running PostgreSQL 7.4.5 (on Gentoo Linux).
All the databases in this scenario were of UNICODE encoding type.
What could be the reson for this, and how can we avoid this?
Thanks in advance,
-Thusitha
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: "UNICODE" error during restoration
@ 2006-06-21 10:57 Thusitha Kodikara <kthusi@yahoo.com>
2006-06-21 16:52 ` Re: "UNICODE" error during restoration Ivo Rossacher <rossacher@bluewin.ch>
0 siblings, 1 reply; 4+ messages in thread
From: Thusitha Kodikara @ 2006-06-21 10:57 UTC (permalink / raw)
To: pgsql-admin
Hello,
We did some more testing and managed to get the dump restored on 7.4.10. Then took a backup and tried to restore on to 7.4.13, but if failed again giving the same errors.
In addition to this we took a dump of an existing DB on 7.4.13 and tried to restore it onto 7.4.13 itself. This also failed.
Could it be that our data contain some invalid characters (even though we never came across any problem before installing the patch 7.4.13) ? In all these instances our encoding was UNICODE.
Does anyone have a clue how to solve this?
Thanks.
-Thusitha
TK <kthusi@yahoo.com> wrote: Hi,
We took a dump of a database running PostgreSQL 7.3.10 (on Gentoo Linux).
We tried to restore it onto a server running PostgreSQL 7.4.13 (on Gentoo Linux). This resulted in the following errors:
psql:<stdin>:13856: ERROR: invalid byte sequence for encoding "UNICODE": 0x85
....
psql:<stdin>:537916: ERROR: invalid byte sequence for encoding "UNICODE": 0xa0
...
psql:<stdin>:1009873: ERROR: invalid byte sequence for encoding "UNICODE": 0x92
...
etc.
We tried to restore the same dump on a server running PostgreSQL 7.3.9 (on Gentoo Linux) and the restoration was successful.
It also worked without any problem on a server running PostgreSQL 7.4.5 (on Gentoo Linux).
All the databases in this scenario were of UNICODE encoding type.
What could be the reson for this, and how can we avoid this?
Thanks in advance,
-Thusitha
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: "UNICODE" error during restoration
2006-06-21 10:57 Re: "UNICODE" error during restoration Thusitha Kodikara <kthusi@yahoo.com>
@ 2006-06-21 16:52 ` Ivo Rossacher <rossacher@bluewin.ch>
2006-06-23 06:12 ` Re: "UNICODE" error during restoration Thusitha Kodikara <kthusi@yahoo.com>
0 siblings, 1 reply; 4+ messages in thread
From: Ivo Rossacher @ 2006-06-21 16:52 UTC (permalink / raw)
To: pgsql-admin
In the HISTORY file comming with the source code there are several
modifications noted related to characterset handling in general and to
unicode more specificaly in the versions before and 7.4.13 it self. The
bottom line is that postgresql in earlier versions did allow incorrect
UNICODE sequences. The recent releases do handle UNICODE stricly according to
the rouls and will not allow incorrect sequences. When you now do have a
backup with incorrect sequences in, you will get this error messages. You can
fix this by fixing the wrong sequences within the dump manually or by a tool
like recode.
Best regards
Ivo Rossacher
Am Mittwoch, 21. Juni 2006 12.57 schrieb Thusitha Kodikara:
> Hello,
>
> We did some more testing and managed to get the dump restored on 7.4.10.
> Then took a backup and tried to restore on to 7.4.13, but if failed again
> giving the same errors.
>
> In addition to this we took a dump of an existing DB on 7.4.13 and tried to
> restore it onto 7.4.13 itself. This also failed.
>
> Could it be that our data contain some invalid characters (even though we
> never came across any problem before installing the patch 7.4.13) ? In all
> these instances our encoding was UNICODE.
>
> Does anyone have a clue how to solve this?
>
> Thanks.
> -Thusitha
>
> TK <kthusi@yahoo.com> wrote: Hi,
>
> We took a dump of a database running PostgreSQL 7.3.10 (on Gentoo Linux).
>
> We tried to restore it onto a server running PostgreSQL 7.4.13 (on Gentoo
> Linux). This resulted in the following errors:
>
> psql:<stdin>:13856: ERROR: invalid byte sequence for encoding "UNICODE":
> 0x85 ....
> psql:<stdin>:537916: ERROR: invalid byte sequence for encoding "UNICODE":
> 0xa0 ...
> psql:<stdin>:1009873: ERROR: invalid byte sequence for encoding "UNICODE":
> 0x92 ...
> etc.
>
> We tried to restore the same dump on a server running PostgreSQL 7.3.9 (on
> Gentoo Linux) and the restoration was successful. It also worked without
> any problem on a server running PostgreSQL 7.4.5 (on Gentoo Linux).
>
> All the databases in this scenario were of UNICODE encoding type.
>
> What could be the reson for this, and how can we avoid this?
>
> Thanks in advance,
>
> -Thusitha
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: "UNICODE" error during restoration
2006-06-21 10:57 Re: "UNICODE" error during restoration Thusitha Kodikara <kthusi@yahoo.com>
2006-06-21 16:52 ` Re: "UNICODE" error during restoration Ivo Rossacher <rossacher@bluewin.ch>
@ 2006-06-23 06:12 ` Thusitha Kodikara <kthusi@yahoo.com>
0 siblings, 0 replies; 4+ messages in thread
From: Thusitha Kodikara @ 2006-06-23 06:12 UTC (permalink / raw)
To: Ivo Rossacher <rossacher@bluewin.ch>; pgsql-admin
Thanks Ivo.
Ivo Rossacher <rossacher@bluewin.ch> wrote: In the HISTORY file comming with the source code there are several
modifications noted related to characterset handling in general and to
unicode more specificaly in the versions before and 7.4.13 it self. The
bottom line is that postgresql in earlier versions did allow incorrect
UNICODE sequences. The recent releases do handle UNICODE stricly according to
the rouls and will not allow incorrect sequences. When you now do have a
backup with incorrect sequences in, you will get this error messages. You can
fix this by fixing the wrong sequences within the dump manually or by a tool
like recode.
Best regards
Ivo Rossacher
Am Mittwoch, 21. Juni 2006 12.57 schrieb Thusitha Kodikara:
> Hello,
>
> We did some more testing and managed to get the dump restored on 7.4.10.
> Then took a backup and tried to restore on to 7.4.13, but if failed again
> giving the same errors.
>
> In addition to this we took a dump of an existing DB on 7.4.13 and tried to
> restore it onto 7.4.13 itself. This also failed.
>
> Could it be that our data contain some invalid characters (even though we
> never came across any problem before installing the patch 7.4.13) ? In all
> these instances our encoding was UNICODE.
>
> Does anyone have a clue how to solve this?
>
> Thanks.
> -Thusitha
>
> TK wrote: Hi,
>
> We took a dump of a database running PostgreSQL 7.3.10 (on Gentoo Linux).
>
> We tried to restore it onto a server running PostgreSQL 7.4.13 (on Gentoo
> Linux). This resulted in the following errors:
>
> psql::13856: ERROR: invalid byte sequence for encoding "UNICODE":
> 0x85 ....
> psql::537916: ERROR: invalid byte sequence for encoding "UNICODE":
> 0xa0 ...
> psql::1009873: ERROR: invalid byte sequence for encoding "UNICODE":
> 0x92 ...
> etc.
>
> We tried to restore the same dump on a server running PostgreSQL 7.3.9 (on
> Gentoo Linux) and the restoration was successful. It also worked without
> any problem on a server running PostgreSQL 7.4.5 (on Gentoo Linux).
>
> All the databases in this scenario were of UNICODE encoding type.
>
> What could be the reson for this, and how can we avoid this?
>
> Thanks in advance,
>
> -Thusitha
---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
^ permalink raw reply [nested|flat] 4+ messages in thread
end of thread, other threads:[~2006-06-23 06:12 UTC | newest]
Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2006-06-19 11:27 "UNICODE" error during restoration TK <kthusi@yahoo.com>
2006-06-21 10:57 Re: "UNICODE" error during restoration Thusitha Kodikara <kthusi@yahoo.com>
2006-06-21 16:52 ` Ivo Rossacher <rossacher@bluewin.ch>
2006-06-23 06:12 ` Thusitha Kodikara <kthusi@yahoo.com>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox