| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Corey Huinker <corey(dot)huinker(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: PSQL commands: \quit_if, \quit_unless |
| Date: | 2016-12-19 18:23:49 |
| Message-ID: | 20161219182349.uqumdmrcyxlwirk6@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
David G. Johnston wrote:
> Being able to do more conditional work in psql would make setting up more
> robust scripts easier and without either losing transaction capabilities or
> session pooling for improved performance when large numbers of small
> commands are run in between flow control in done in bash.
Have you tried to script processes in shell using a single background
psql process with which the shell code communicates using a pipe? I've
long been curious about that approach, but never had a strong need
enough to actually write the code. It should be possible.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2016-12-19 18:36:04 | Re: PSQL commands: \quit_if, \quit_unless |
| Previous Message | Corey Huinker | 2016-12-19 18:14:27 | Re: PSQL commands: \quit_if, \quit_unless |