From: | Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM> |
---|---|
To: | "Harvey, Allan AC" <HarveyA(at)OneSteel(dot)com> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: Upgrade from 7.4.5 to 8.3.3 |
Date: | 2008-10-30 14:46:14 |
Message-ID: | 4909C8B6.9070706@sun.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Harvey, Allan AC napsal(a):
> Zdenek,
>
>> Hmm, It does not look good. Your OS does not return proper
>> information about
>> codeset. Following code is broken:
>>
>> setlocale(LC_CTYPE, ctype);
>> sys = nl_langinfo(CODESET);
>> sys = strdup(sys);
>>
>> See
>> http://www.opengroup.org/onlinepubs/009695399/functions/nl_lan
> ginfo.html
>
>> It seems you need to fix OS first. After that we can add CODESET mapping to
>> PostgreSQL.
>
>> Zdenek
>
> I don't think this is possible.
>
> Can you give me an indication what problems I should look out for?
> Regression testing only showed some date format issues if I remeber correctly.
>
I think, problem could be on two places:
1) libc is broken and does not return correct values.
2) locale definition does not contain CODESET information.
Do you use system libc or glibc? You can try create own locale by localedef and
test what happen.
Zdenek
From | Date | Subject | |
---|---|---|---|
Next Message | Zdenek Kotala | 2008-10-30 15:27:11 | Re: BUG #4496: Memory leak in pg_dump.c? |
Previous Message | Tom Lane | 2008-10-30 14:39:58 | Re: Bug #3924: Create Database with another encoding as the encoding from postgres |