| From: | Dominique Devienne <ddevienne(at)gmail(dot)com> |
|---|---|
| To: | Daniel Verite <daniel(at)manitou-mail(dot)org> |
| Cc: | david(dot)g(dot)johnston(at)gmail(dot)com, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: COPY TO STDOUT WITH (FORMAT CSV, HEADER), and embedded newlines |
| Date: | 2022-03-11 20:16:17 |
| Message-ID: | CAFCRh-9Fb97c59NysfYfdVUcKwd3pPfMwTdu5uaEwfPnd7cCCQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, Mar 11, 2022 at 8:32 PM Daniel Verite <daniel(at)manitou-mail(dot)org> wrote:
> 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
I actually just submitted CSV+PostProcessing :)
But sure, if TEXT does the kind of pseudo-CSV I need, I'd change it to use it.
I'll look into it next week. Thanks again Daniel. --DD
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Lewis | 2022-03-12 03:03:09 | Re: foreign key on delete cascade order? |
| Previous Message | Daniel Verite | 2022-03-11 19:32:02 | Re: COPY TO STDOUT WITH (FORMAT CSV, HEADER), and embedded newlines |