Postgres Pro
Downloads
Home   >   mailing lists

Re: csv format for psql - Mailing list pgsql-hackers

From David G. Johnston
Subject Re: csv format for psql
Date
Msg-id CAKFQuwbuO_WdHp1qS2QtG7FqSsV_nHwum06QdJ7=KuzWycvHZg@mail.gmail.com
Whole thread Raw
In response to Re: csv format for psql  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses Re: csv format for psql
List pgsql-hackers
Tree view
On Sunday, June 3, 2018, Pavel Stehule <pavel.stehule@gmail.com> wrote:

\pset fieldsep ;
\pset format csv

I don't like when one command overwrite settings of some other command. We can introduce some similar like GUC where default values from configure file can be overwritten by custom setting for session. So I am able to thinking about some settings

like

\pset csv_default_separator
\pset csv_default_header

Then there is question to simplify all and use \pset csv_separator, and csv format independent of fieldseparator value? It is possible, but I don't think so have more option for similar value is good idea (for interactive mode).

Having a dedicated option seems infinitely better than adding new settings for defaults and having to keep track of whether the shared field separator is a default versus a user specified value.

Recently we reworked server GUCs to avoid this kind of unset/default behavior.  I don't see how introducing or relying upon it in psql would be an advantage.

At this point -1, keep the status quo, for any implementation that tries to make the unaligned mode field separator perform double duty.  I'm open, but unlikely, to be convinced that it can be done without unforeseen bad side effects and degraded usability.

David J.

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: why partition pruning doesn't work?
Next
From: "MauMau"
Date:
Subject: Re: New committers announced at PGCon 2018