MIME-Version: 1.0
References: <43b9fb8c.8b5c.197f96e3544.Coremail.gzhcoder@126.com>
In-Reply-To: <43b9fb8c.8b5c.197f96e3544.Coremail.gzhcoder@126.com>
From: Ron Johnson <ronljohnsonjr@gmail.com>
Date: Fri, 11 Jul 2025 09:07:32 -0400
Message-ID: <CANzqJaB24YUU-toCxGWVUym2Fas2QATYhuZCM3M0ZHfkmcFMbw@mail.gmail.com>
Subject: Re: Question Regarding COPY Command Handling of Line Breaks in PostgreSQL
To: "pgsql-generallists.postgresql.org" <pgsql-general@lists.postgresql.org>
Content-Type: multipart/alternative; boundary="000000000000e1865b0639a6fe61"
Archived-At: <https://www.postgresql.org/message-id/CANzqJaB24YUU-toCxGWVUym2Fas2QATYhuZCM3M0ZHfkmcFMbw%40mail.gmail.com>
Precedence: bulk

--000000000000e1865b0639a6fe61
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Fri, Jul 11, 2025 at 8:20=E2=80=AFAM 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)?

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

--000000000000e1865b0639a6fe61
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Fri, Jul 11, 2025 at 8:20=E2=80=AFAM g=
zh &lt;<a href=3D"mailto:gzhcoder@126.com">gzhcoder@126.com</a>&gt; wrote:<=
/div><div class=3D"gmail_quote gmail_quote_container"><blockquote class=3D"=
gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(20=
4,204,204);padding-left:1ex"><div style=3D"line-height:1.7;color:rgb(0,0,0)=
;font-size:14px;font-family:Arial"><div>Dear,</div><div><br></div><div>I am=
 encountering an issue with the COPY command in PostgreSQL regarding the ha=
ndling of line breaks in data fields. My PostgreSQL instance is installed o=
n a Linux system.</div><div><br></div><div>When I use the COPY command to e=
xport data to a CSV file and then import the same CSV file back into the da=
tabase, all carriage return characters (CR) in the fields are automatically=
 converted to line feed characters (LF). For example:</div><div><br></div><=
div>Field content before import: *** (CR) ***</div><div>Field content after=
 import: *** (LF) ***</div><div>I would like to know if there is a way to u=
se the COPY command while preserving the original line breaks (CR) in the d=
ata fields during import.</div></div></blockquote><div>=C2=A0</div></div><d=
iv>What PG version?</div><div>What&#39;s the full command (including both s=
hell and SQL commands)?</div><div><br></div><span class=3D"gmail_signature_=
prefix">-- </span><br><div dir=3D"ltr" class=3D"gmail_signature"><div dir=
=3D"ltr">Death to &lt;Redacted&gt;, and butter sauce.<div>Don&#39;t boil me=
, I&#39;m still alive.<br><div><div>&lt;Redacted&gt; lobster!</div></div></=
div></div></div></div>

--000000000000e1865b0639a6fe61--