Re: COPY TO STDOUT WITH (FORMAT CSV, HEADER), and embedded newlines - Mailing list pgsql-general

From Daniel Verite
Subject Re: COPY TO STDOUT WITH (FORMAT CSV, HEADER), and embedded newlines
Date
Msg-id 52dc26c2-e3ba-4d12-811a-6bfd04c35bc5@manitou-mail.org
Whole thread Raw
In response to Re: COPY TO STDOUT WITH (FORMAT CSV, HEADER), and embedded newlines  (Dominique Devienne <ddevienne@gmail.com>)
Responses Re: COPY TO STDOUT WITH (FORMAT CSV, HEADER), and embedded newlines
List pgsql-general
    Dominique Devienne wrote:


> so I can easily do that "\n" encoding myself, as a post-processing on
> the buffer I get back.

Alternatively, it might be easier to use the default TEXT format of
COPY rather than CSV, as the TEXT format already produces \n for
line feeds, along with    half a dozen other special backslashes sequences.
See https://www.postgresql.org/docs/current/sql-copy.html


Best regards,
--
Daniel Vérité
https://postgresql.verite.pro/
Twitter: @DanielVerite



pgsql-general by date:

Previous
From: Dominique Devienne
Date:
Subject: Re: COPY TO STDOUT WITH (FORMAT CSV, HEADER), and embedded newlines
Next
From: Dominique Devienne
Date:
Subject: Re: COPY TO STDOUT WITH (FORMAT CSV, HEADER), and embedded newlines