| From: | Corey Huinker <corey(dot)huinker(at)gmail(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | vignesh C <vignesh21(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Add SHELL_EXIT_CODE to psql |
| Date: | 2023-01-23 18:59:29 |
| Message-ID: | CADkLM=eccA8yyLr8m1LP0sXvpdCrQqCH1YJ3bX50=cAhF6xi5A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Jan 20, 2023 at 8:54 AM Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Wed, Jan 4, 2023 at 2:09 AM Corey Huinker <corey(dot)huinker(at)gmail(dot)com>
> wrote:
> > 2. There are now two psql variables, SHELL_EXIT_CODE, which has the
> return code, and SHELL_ERROR, which is a true/false flag based on whether
> the exit code was nonzero. These variables are the shell result analogues
> of SQLSTATE and ERROR.
>
> Seems redundant.
>
SHELL_ERROR is helpful in that it is a ready-made boolean that works for
\if tests in the same way that ERROR is set to true any time SQLSTATE is
nonzero. We don't yet have inline expressions for \if so the ready-made
boolean is a convenience.
Or are you suggesting that I should have just set ERROR itself rather than
create SHELL_ERROR?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2023-01-23 19:05:33 | Re: Non-superuser subscription owners |
| Previous Message | Nikita Malakhov | 2023-01-23 18:54:15 | Re: run pgindent on a regular basis / scripted manner |