Re: BUG #5361: KOI8U issue

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Alexender <bavcom(at)mail(dot)ru>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5361: KOI8U issue
Date: 2010-03-04 13:41:52
Message-ID: 1267710112.14949.3.camel@fsopti579.F-Secure.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On tor, 2010-03-04 at 07:31 +0000, Alexender wrote:
> This is real problem.
> Dump from Postgres 8.2 can't be restored in Postgres 8.4
> if I use on server 8.2 encodings KOI8 and --lc-collate and --lc-ctype
> uk_UA.KOI8-U
> Because conversion is not supported between KOI8R and KOI8U and
> dump 8.2 have string "SET client encodigs KOI8" which KOI8R in 8.4 but I
> need in postgres 8.4 "SET client encodigs KOI8U" in dump file because i used
> --lc-collate and --lc-ctype = uk_UA.koi8-U.
>
> [Solved]
> The only way I solve it change in plain/text dump string
> on "SET client encodings KOI8U" and use database in koi8U encoding with
> --lc-collate and --lc-ctype = uk_UA.koi8-U.
> But it's dfficult to change it in large file.

Collation support was tightened in 8.4; a lot of users are affected by
similar problems. Technically, you shouldn't have used a KOI8U locale
in 8.2 to begin with, because that encoding wasn't supported by
PostgreSQL back then. Only that 8.2 didn't check that.

It would be fairly simple to create conversion support between KOI8R and
KOI8U, if you would like to look into that.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Peter Eisentraut 2010-03-04 14:15:29 Re: PostgreSQL-9.0alpha: jade required?
Previous Message ALEX 2010-03-04 10:55:14 BUG #5362: WARNING could not determine encoding