From: | Rory Campbell-Lange <rory(at)campbell-lange(dot)net> |
---|---|
To: | Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> |
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:47:32 |
Message-ID: | 20200327224732.GA28471@campbell-lange.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 27/03/20, Andrew Gierth (andrew(at)tao11(dot)riddles(dot)org(dot)uk) wrote:
> >>>>> "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.
My apologies. I missed the subtlety of the substitution in your perl code.
From | Date | Subject | |
---|---|---|---|
Next Message | Jerry Sievers | 2020-03-27 23:26:39 | Re: Promoting Hot standby after running select pg_xlog_replay_pause(); |
Previous Message | Andrew Gierth | 2020-03-27 22:32:48 | Re: \COPY to accept non UTF-8 chars in CHAR columns |