Re: proposal \gcsv - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: proposal \gcsv
Date
Msg-id CAFj8pRAWeUcwu+HDVR+7mhRXZP8kSMVq46xDORi7BJRLJ_CcHg@mail.gmail.com
Whole thread Raw
In response to Re: proposal \gcsv  ("Daniel Verite" <daniel@manitou-mail.org>)
Responses Re: proposal \gcsv
Re: proposal \gcsv
List pgsql-hackers


st 1. 4. 2020 v 17:52 odesílatel Daniel Verite <daniel@manitou-mail.org> napsal:
        Tom Lane wrote:

>  I could see having a command to copy the current primary formatting
> parameters to the alternate area, too.

We could have a stack to store parameters before temporary
changes, for instance if you want to do one csv export and
come back to normal without assuming what "normal"
values were.

\pset push format csv_fieldsep
\pset format csv
\pset  csv_fielsep '\t'
some command \g somefile
\pset pop

So \pset pop would reset the pushed parameters
to their values when pushed, which also could be all
parameters:

\pset push all
\pset param1 something
\pset param2 something-else
...other commands...
\pset pop

or

\pset push all
\i somescript.sql
\pset pop


It can work, but it is not user friendly - my proposal was motivated by using some quick csv exports to gplot's pipe.

Regards

Pavel

Best regards,
--
Daniel Vérité
PostgreSQL-powered mailer: http://www.manitou-mail.org
Twitter: @DanielVerite

pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: snapshot too old issues, first around wraparound and then more.
Next
From: David Steele
Date:
Subject: Re: pgbench - add pseudo-random permutation function