| From: | Vik Fearing <vik(at)postgresfriends(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | Daniel Verite <daniel(at)manitou-mail(dot)org>, Erik Rijkers <er(at)xs4all(dot)nl>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: proposal \gcsv |
| Date: | 2020-04-01 07:07:26 |
| Message-ID: | 3d49e69a-b674-1295-c55e-1e9875c38813@postgresfriends.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dilip Kumar | 2020-04-01 07:11:38 | Re: pg_stat_statements issue with parallel maintenance (Was Re: WAL usage calculation patch) |
| Previous Message | Andres Freund | 2020-04-01 06:40:08 | snapshot too old issues, first around wraparound and then more. |