Re: How to *really* quit psql? - Mailing list pgsql-hackers

From David G. Johnston
Subject Re: How to *really* quit psql?
Date
Msg-id CAKFQuwYJ3jww83LEhy4CnTvZZgSyXjhk6tY7cjDuaVkg252Adg@mail.gmail.com
Whole thread Raw
In response to Re: How to *really* quit psql?  ("David G. Johnston" <david.g.johnston@gmail.com>)
Responses Re: How to *really* quit psql?
List pgsql-hackers
On Sat, Nov 19, 2022 at 12:59 PM David G. Johnston <david.g.johnston@gmail.com> wrote:
On Sat, Nov 19, 2022 at 12:49 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
Greg Stark <stark@mit.edu> writes:
> On Sat, 19 Nov 2022 at 14:10, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Under what circumstances would it be appropriate for a script to take
>> it on itself to decide that?  It has no way of knowing what the next -f
>> option is or what the user intended.

> Presumably when they're written by the same person so the script does
> effectively know what the "user" intended because it's written by the
> same user.

Even so, embedding that knowledge in the first script doesn't seem
like the sort of design we ought to encourage.  It'd be better if
"don't run the next script if the first one fails" were directed
by a command-line switch or the like.  I also wonder exactly how
this interacts with existing features like ON_ERROR_STOP.

vagrant@vagrant:~$ /usr/local/pgsql/bin/psql -v ON_ERROR_STOP=1 -f two.psql -f three.psql postgres
psql:two.psql:1: ERROR:  division by zero
vagrant@vagrant:~$ /usr/local/pgsql/bin/psql -f two.psql -f three.psql postgres
psql:two.psql:1: ERROR:  division by zero
 ?column?
----------
        2
(1 row)

 ?column?
----------
        3
(1 row)


Sorry, forgot the \quit test:

vagrant@vagrant:~$ /usr/local/pgsql/bin/psql -v ON_ERROR_STOP=1 -f two.psql -f three.psql postgres
 ?column?
----------
        2
(1 row)

 ?column?
----------
        3
(1 row)

(there is a \quit at the end of two.psql)

David J.

pgsql-hackers by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: How to *really* quit psql?
Next
From: David Geier
Date:
Subject: Re: Reduce timing overhead of EXPLAIN ANALYZE using rdtsc?