Re: proposal \gcsv - Mailing list pgsql-hackers

From Vik Fearing
Subject Re: proposal \gcsv
Date
Msg-id 3d49e69a-b674-1295-c55e-1e9875c38813@postgresfriends.org
Whole thread Raw
In response to Re: proposal \gcsv  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: proposal \gcsv  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 4/1/20 1:53 AM, Tom Lane wrote:
> Consider some syntax along the lines of
> 
> \gpset (pset-option-name [pset-option-value]) ... filename
> 
> or if you don't like parentheses, choose some other punctuation to wrap
> the \pset options in.  I initially thought of square brackets, but I'm
> afraid they might be just too darn confusing to document --- how could
> you make them distinct from metasyntax square brackets, especially in
> plain-ASCII docs?  Also it'd have to be punctuation that's unlikely to
> start a file name --- but parens are already reserved in most shells.


If parens are going to be required, why don't we just add them to \g?

TABLE blah \g (format csv) filename
-- 
Vik Fearing



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: snapshot too old issues, first around wraparound and then more.
Next
From: Dilip Kumar
Date:
Subject: Re: pg_stat_statements issue with parallel maintenance (Was Re: WALusage calculation patch)