Re: \COPY to accept non UTF-8 chars in CHAR columns

From: Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>
To: Rory Campbell-Lange <rory(at)campbell-lange(dot)net>
Cc: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Matthias Apitz <guru(at)unixarea(dot)de>, "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: \COPY to accept non UTF-8 chars in CHAR columns
Date: 2020-03-27 22:32:48
Message-ID: 87ftdta0qs.fsf@news-spur.riddles.org.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

>>>>> "Rory" == Rory Campbell-Lange <rory(at)campbell-lange(dot)net> writes:

Rory> Or:

Rory> iconv -f WINDOWS-1252 -t UTF-8 -c < tempfile2 > tempfile3

No. That's just a conversion of win1252 to utf8 without regard for any
UTF8 that might already be present in the input. Any such input will end
up double-encoded, requiring further work to fix.

--
Andrew (irc:RhodiumToad)

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Rory Campbell-Lange 2020-03-27 22:47:32 Re: \COPY to accept non UTF-8 chars in CHAR columns
Previous Message Rory Campbell-Lange 2020-03-27 22:18:35 Re: \COPY to accept non UTF-8 chars in CHAR columns