| From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Greg Stark <stark(at)mit(dot)edu>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: How to *really* quit psql? |
| Date: | 2022-11-20 07:54:53 |
| Message-ID: | e1bc99e-5726-2133-adac-faff8b802213@mines-paristech.fr |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hello David,
> vagrant(at)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)
Yep, that summarizes my issues!
ON_ERROR_STOP is only of SQL errors, so a script can really stop by having
an intentional SQL error.
--
Fabien.
| Attachment | Content-Type | Size |
|---|---|---|
| quit.sql | application/sql | 78 bytes |
| error.sql | application/sql | 65 bytes |
| include.sql | application/sql | 145 bytes |
| exit.sql | application/sql | 66 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fabien COELHO | 2022-11-20 08:01:59 | Re: How to *really* quit psql? |
| Previous Message | Fabien COELHO | 2022-11-20 07:42:35 | Re: How to *really* quit psql? |