| From: | Erik Rijkers <er(at)xs4all(dot)nl> | 
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> | 
| Cc: | Vik Fearing <vik(at)postgresfriends(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> | 
| Subject: | Re: proposal \gcsv | 
| Date: | 2020-03-26 18:41:45 | 
| Message-ID: | 50f6629d738fa4861c7e29e391fd9569@xs4all.nl | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-hackers | 
On 2020-03-26 18:49, Pavel Stehule wrote:
> Hi
> 
> [psql-gfmt.patch]
This seems useful and works well; I haven't found any errors. Well done.
However, I have a suggestion that is perhaps slightly outside of this 
patch but functionally so close that maybe we can discuss it here.
When you try to get a tab-separated output via this new  \gfmt  in a 
one-liner
you're still forced to use
    \pset csv_fieldsep '\t'
Would it be possible to do one of the following to enable a more compact 
one-liner syntax:
1. add an option:
     \gfmt tsv   --> use a TAB instead of a comma in the csv
or
2. let the psql command-line option '--csv' honour the value given by  
psql -F/--field-separator (it does not do so now)
or
3. add an psql -commandline option:
     --csv-field-separator
Any of these three (I'd prefer the first) would make producing a tsv in 
shell one-liners with psql easier/more compact.
Thanks,
Erik Rijkers
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2020-03-26 18:49:47 | Re: plan cache overhead on plpgsql expression | 
| Previous Message | Tom Lane | 2020-03-26 18:37:59 | Re: plan cache overhead on plpgsql expression |