public inbox for [email protected]
help / color / mirror / Atom feedFrom: Ron Johnson <[email protected]>
To: pgsql-generallists.postgresql.org <[email protected]>
Subject: Re: Question Regarding COPY Command Handling of Line Breaks in PostgreSQL
Date: Fri, 11 Jul 2025 09:07:32 -0400
Message-ID: <CANzqJaB24YUU-toCxGWVUym2Fas2QATYhuZCM3M0ZHfkmcFMbw@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
On Fri, Jul 11, 2025 at 8:20 AM gzh <[email protected]> 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!
view thread (2+ messages)
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected]
Subject: Re: Question Regarding COPY Command Handling of Line Breaks in PostgreSQL
In-Reply-To: <CANzqJaB24YUU-toCxGWVUym2Fas2QATYhuZCM3M0ZHfkmcFMbw@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox