From: | Tino Wildenhain <tino(at)wildenhain(dot)de> |
---|---|
To: | Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> |
Cc: | john(at)geeknet(dot)com(dot)au, linux(at)alteeve(dot)com, Postgresql-General <pgsql-general(at)postgresql(dot)org>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [HACKERS] Invalid unicode in COPY problem |
Date: | 2005-05-08 07:18:29 |
Message-ID: | 1115536709.23152.5.camel@Andrea.peacock.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
Am Sonntag, den 08.05.2005, 14:30 +0900 schrieb Tatsuo Ishii:
...
> Actually I myself thought as you are before. Later I found that it was
> not so good idea. People already have invalid encoded data in their
> precious database and have very hard time to migrate to newer version
> of PostgreSQL because of encoding validation.
...
> Now I need to upgrade to newer PostgreSQL within 1 day. I know I have
> to fix wrong encoded field but it will take more than 1 day. So I
> would like to import the data first then fix wrong encoded field on
> running database since I can reach members by phone or email even with
> wrong encoded address field...
Well, if you are so in a hurry you better not migrate. Postgres is
proud of validating the input and to have no invalid data. So if
you have invalid data, better fix it.
> I saw this kind of situation in the real world and that's why we
> developed the patches.
Why not developing a helper for contrib to help reencoding the
database instead?
Regards
Tino
From | Date | Subject | |
---|---|---|---|
Next Message | John Hansen | 2005-05-08 08:55:21 | Re: [HACKERS] Invalid unicode in COPY problem |
Previous Message | Tatsuo Ishii | 2005-05-08 05:30:45 | Re: [HACKERS] Invalid unicode in COPY problem |
From | Date | Subject | |
---|---|---|---|
Next Message | John Hansen | 2005-05-08 08:47:25 | Re: Patch for collation using ICU |
Previous Message | Marc G. Fournier | 2005-05-08 06:17:59 | Re: Can we get patents? |