From: Vivek Khera <khera@kcilink.com>
To: pgsql-performance@postgresql.org
Subject: restoring to wrong encoding db
Date: Fri, 03 Sep 2004 15:42:44 -0400
Message-ID: <x7brgni1fv.fsf@yertle.int.kciLink.com> (raw)
I was just copying a database that was in UNICODE encoding into a new
db for some testing. I hand't realized it was UNICODE and when it hit
some funky chinese data (from some spam that came in...) it errored
out with a string too long for a varchar(255).
The dump was created on PG 7.4.3 with "pg_dump -Fc"
The db was created with "createdb rt3"
The restore was to PG 7.4.5 with "pg_restore --verbose -d rt3 rt3.dump"
Is there some way for the dump to notice that the encoding is wrong in
the db into which it is being restored? Once I created the rt3 db
with encoding='UNICODE' it worked just fine. Should there be some
kind of check like that?
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Vivek Khera, Ph.D. Khera Communications, Inc.
Internet: khera@kciLink.com Rockville, MD +1-301-869-4449 x806
AIM: vivekkhera Y!: vivek_khera http://www.khera.org/~vivek/
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: khera@kcilink.com
Subject: Re: restoring to wrong encoding db
In-Reply-To: <x7brgni1fv.fsf@yertle.int.kciLink.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
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