Re: COPY TO CSV produces data that is incompatible/unsafe for \COPY FROM CSV

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Noah Misch <noah(at)leadboat(dot)com>, Svante Richter <pgsql-bugs(at)richter(dot)id>, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: COPY TO CSV produces data that is incompatible/unsafe for \COPY FROM CSV
Date: 2023-11-03 17:58:21
Message-ID: ZUU0vU0OS4XFpnOV@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Sat, Oct 28, 2023 at 11:38:37AM -0400, Bruce Momjian wrote:
> On Tue, Aug 16, 2022 at 11:26:47AM -0400, Bruce Momjian wrote:
> > I think at this point we should either fix this or document it.
>
> I have decided to document this with the attached patch. I plan to
> apply it to all supported Postgres versions. If we ever fix FROM file
> so only FROM STDIN is a problem, we can update the documentation.

Patch applied to all supported versions.

--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com

Only you can decide what is important to you.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Michael Paquier 2023-11-06 04:54:31 Re: BUG #18179: Cluster History Error
Previous Message Robert Leach 2023-11-03 17:49:43 Re: BUG #18177: certain queries under certain contexts take multiple orders of magnitude longer compared to v10