From: | Arnaud Lesauvage <thewild(at)freesurf(dot)fr> |
---|---|
To: | Arnaud Lesauvage <thewild(at)freesurf(dot)fr> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: MSSQL to PostgreSQL : Encoding problem |
Date: | 2006-11-23 17:05:02 |
Message-ID: | 4565D4BE.9000707@freesurf.fr |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Arnaud Lesauvage a écrit :
> Brandon Aiken a écrit :
>> It also might be a big/little endian problem, although I always thought that was platform specific, not locale specific.
>>
>> Try the UCS-2-INTERNAL and UCS-4-INTERNAL codepages in iconv, which should use the two-byte or four-byte versions of UCS encoding using the system's default endian setting.
>
>
> Guys, it worked !!!!
> UCS-4-INTERNAL was the right choice !!!
>
> I love you all !
>
> (now I just have an out of memory problem, but that's going
> to be a new thread)
Guys, it did not work !!! :(
I thought it worked because postgres seemed to be loading
the file and failing at the end with an "out of memory"
error, but in fact I think the conversion remove all
end-of-line characters (one line of 1.5GB was too much for
COPY...).
Still searching !
--
Arnaud
From | Date | Subject | |
---|---|---|---|
Next Message | Tomi NA | 2006-11-23 17:15:59 | Re: MSSQL to PostgreSQL : Encoding problem |
Previous Message | Arnaud Lesauvage | 2006-11-23 16:57:58 | Re: COPY FROM : out of memory |