| From: | Corey Huinker <corey(dot)huinker(at)gmail(dot)com> |
|---|---|
| To: | tgl(at)sss(dot)pgh(dot)pa(dot)us |
| Cc: | coelho(at)cri(dot)ensmp(dot)fr, michael(at)paquier(dot)xyz, daniel(at)manitou-mail(dot)org, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: csv format for psql |
| Date: | 2018-11-26 04:56:56 |
| Message-ID: | CADkLM=e=-hbNJB-7_CjJWEXa9hRQhSfz+nTpYViP0Ft38-R9nQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, Nov 25, 2018 at 11:23 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Corey Huinker <corey(dot)huinker(at)gmail(dot)com> writes:
> > Could we have another output type called "separated" that uses the
> existing
> > --fieldsep / --recordsep?
>
> Uh, what's the difference from the existing unaligned format?
>
No footer and I guess we'd want to escape instances of fieldsep and
recordsep in the data, so I guess if we had an option to escape instances
of fieldsep/recordsep found in the data, unaligned would work fine.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Langote | 2018-11-26 04:58:08 | Re: using expression syntax for partition bounds |
| Previous Message | Pavel Stehule | 2018-11-26 04:53:05 | Re: csv format for psql |