Re: csv format for psql

From: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Daniel Verite <daniel(at)manitou-mail(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: csv format for psql
Date: 2018-11-07 09:01:20
Message-ID: alpine.DEB.2.21.1811070951470.2681@lancre
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


Bonjour Michaël,

> First, it seems to me that it is necessary to overcomplicate the
> interface of psql for that. Most of the other formats don't have their
> own switch, and it is perfectly possible to use CSV format with just
> --pset=format=csv.

Although this work, it is not very user friendly nor easy to memorize.

Quite a few direct format options already exists, eg -A --no-align (yuk,
-A means not to align... :-(), -H --html...

In this context "--csv" looks pretty unambiguous and more useful, so I
would be in favor of keeping this option.

> -C could also be useful for other things, say compression.

Sure. -C is *NOT* used for --csv in the patch, although it may have been
with an earlier version?

> In the regression tests, "col 9" is wanted with a newline?

Yes, the point is to check whether quoting & escaping are triggered
appropriately in column names and values.

--
Fabien.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alexey Kondratov 2018-11-07 09:58:11 Re: [Patch] pg_rewind: options to use restore_command from recovery.conf or command line
Previous Message Evgeniy Efimkin 2018-11-07 08:48:44 Connection limit doesn't work for superuser