On Fri, Mar 11, 2022 at 8:32 PM Daniel Verite <daniel@xxxxxxxxxxxxxxxx> 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
