| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
| Cc: | Isaac Morland <isaac(dot)morland(at)gmail(dot)com>, Daniel Verite <daniel(at)manitou-mail(dot)org>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, David Steele <david(at)pgmasters(dot)net>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: csv format for psql |
| Date: | 2018-04-06 03:08:34 |
| Message-ID: | 4b5ab370-ea2a-3911-60a4-407c76e85422@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 4/1/18 03:27, Pavel Stehule wrote:
> I don't share option so CSV format should be exactly same like CSV COPY.
> COPY is designed for backups - and header is not too important there.
> When I seen some csv, then there usually header was used.
I think in practice a lot of people use COPY also because it's a nice
way to get CSV output, even if it's not for backups. The options that
COPY has for CSV are clearly designed around making the output
compatible with various CSV-variants. If we create another way to do
CSV in psql, it would be totally confusing if some of the options are
the same and some are different or missing.
Another thought: Isn't CSV just the same as unaligned output plus some
quoting? Could we add a quote character setting and then define --csv
to be quote-character = " and fieldsep = , ?
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2018-04-06 03:20:22 | Re: PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFS |
| Previous Message | Edmund Horner | 2018-04-06 03:01:43 | Re: PATCH: psql tab completion for SELECT |