Re: New "raw" COPY format - Mailing list pgsql-hackers

From Joel Jacobson
Subject Re: New "raw" COPY format
Date
Msg-id 1fb4eba5-e894-49e1-a2a4-f4e360b02a0f@app.fastmail.com
Whole thread Raw
In response to Re: New "raw" COPY format  (Tatsuo Ishii <ishii@postgresql.org>)
List pgsql-hackers
On Sun, Oct 13, 2024, at 11:52, Tatsuo Ishii wrote:
> After copy imported the "unstructured text file" in "row" COPY format,
> what the column type is?  text? or bytea? If it's text, how do you
> handle encoding conversion if the "unstructured text file" is encoded
> in server side unsafe encoding such as SJIS?
>
>>  All characters are taken literally.
>>  There is no special handling for quotes, backslashes, or escape sequences.
>
> If SJIS text is imported "literally" (i.e. no encoding conversion), it
> should be rejected.

I think encoding conversion is still necessary,
and should work the same as for the COPY formats "text" and "csv".

/Joel



pgsql-hackers by date:

Previous
From: Tatsuo Ishii
Date:
Subject: Re: New "raw" COPY format
Next
From: Junwang Zhao
Date:
Subject: Re: general purpose array_sort