Re: MSSQL to PostgreSQL : Encoding problem - Mailing list pgsql-general

From Arnaud Lesauvage
Subject Re: MSSQL to PostgreSQL : Encoding problem
Date
Msg-id 4565D4BE.9000707@freesurf.fr
Whole thread Raw
In response to Re: MSSQL to PostgreSQL : Encoding problem  (Arnaud Lesauvage <thewild@freesurf.fr>)
Responses Re: MSSQL to PostgreSQL : Encoding problem  ("Tomi NA" <hefest@gmail.com>)
List 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
UCSencoding 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

pgsql-general by date:

Previous
From: Arnaud Lesauvage
Date:
Subject: Re: COPY FROM : out of memory
Next
From: "Tomi NA"
Date:
Subject: Re: MSSQL to PostgreSQL : Encoding problem