Re: Upgrade from 7.4.5 to 8.3.3 - Mailing list pgsql-bugs

From Zdenek Kotala
Subject Re: Upgrade from 7.4.5 to 8.3.3
Date
Msg-id 4909C8B6.9070706@sun.com
Whole thread Raw
In response to Re: Upgrade from 7.4.5 to 8.3.3  ("Harvey, Allan AC" <HarveyA@OneSteel.com>)
Responses Re: Upgrade from 7.4.5 to 8.3.3  ("Harvey, Allan AC" <HarveyA@OneSteel.com>)
List 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

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: Bug #3924: Create Database with another encoding as the encoding from postgres
Next
From: Zdenek Kotala
Date:
Subject: Re: BUG #4496: Memory leak in pg_dump.c?