Re: Question Regarding COPY Command Handling of Line Breaks in PostgreSQL - Mailing list pgsql-general

From Ron Johnson
Subject Re: Question Regarding COPY Command Handling of Line Breaks in PostgreSQL
Date
Msg-id CANzqJaB24YUU-toCxGWVUym2Fas2QATYhuZCM3M0ZHfkmcFMbw@mail.gmail.com
Whole thread Raw
In response to Question Regarding COPY Command Handling of Line Breaks in PostgreSQL  (gzh <gzhcoder@126.com>)
Responses Re: Question Regarding COPY Command Handling of Line Breaks in PostgreSQL
List pgsql-general
On Fri, Jul 11, 2025 at 8:20 AM gzh <gzhcoder@126.com> wrote:
Dear,

I am encountering an issue with the COPY command in PostgreSQL regarding the handling of line breaks in data fields. My PostgreSQL instance is installed on a Linux system.

When I use the COPY command to export data to a CSV file and then import the same CSV file back into the database, all carriage return characters (CR) in the fields are automatically converted to line feed characters (LF). For example:

Field content before import: *** (CR) ***
Field content after import: *** (LF) ***
I would like to know if there is a way to use the COPY command while preserving the original line breaks (CR) in the data fields during import.
 
What PG version?
What's the full command (including both shell and SQL commands)?

--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!

pgsql-general by date:

Previous
From: gzh
Date:
Subject: Question Regarding COPY Command Handling of Line Breaks in PostgreSQL
Next
From: Dimitrios Apostolou
Date:
Subject: Re: having temp_tablespaces on less reliable storage