| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Noah Misch <noah(at)leadboat(dot)com> |
| Cc: | Alon <asimantov(at)tableausoftware(dot)com>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: Re: BUG #11431: Failing to backup and restore a Windows postgres database, with Norwegian Bokmål locale. |
| Date: | 2014-09-21 16:13:25 |
| Message-ID: | 7107.1411316005@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | Postg토토 꽁 머니SQL : Postg토토 꽁 머니SQL 메일 링리스트 : 2014-09-21 이후 PGSQL-BUGS 16:13 |
Noah Misch <noah(at)leadboat(dot)com> writes:
> On Fri, Sep 19, 2014 at 03:15:53PM -0700, Alon wrote:
>> The pg_dump file contains this command:
>> CREATE DATABASE workgroup WITH TEMPLATE = template0 ENCODING = 'UTF8'
>> LC_COLLATE = 'Norwegian (Bokml)_Norway.1252' LC_CTYPE = 'Norwegian
>> (Bokml)_Norway.1252';
> In WIN1252, "e5 6c 29" is "l)". We're likely failing to set client_encoding
> at some essential point in the process.
The level of stupidity needed to use non-ASCII characters in a locale name
is breathtaking. What were Microsoft thinking? How are we supposed to
guess what encoding applies when setting the encoding?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Noah Misch | 2014-09-21 18:04:13 | Re: Re: BUG #11431: Failing to backup and restore a Windows postgres database, with Norwegian Bokmål locale. |
| Previous Message | Alon | 2014-09-21 13:38:39 | RE: Re: BUG #11431: Failing to backup and restore a Windows postgres database, with Norwegian Bokmål locale. |