| From: | Grzegorz Jaśkiewicz <gryzman(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: psql exit code, bug ? |
| Date: | 2009-09-16 14:35:36 |
| Message-ID: | 2f4958ff0909160735h6b160354o8cbb6c2e93e52590@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
2009/9/16 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
> =?UTF-8?Q?Grzegorz_Ja=C5=9Bkiewicz?= <gryzman(at)gmail(dot)com> writes:
>> Looks like psql loves to report on errors, only when -c is used,
>> otherwise return code is always 0...
>
> The documentation seems perfectly clear on this point:
>
> psql returns 0 to the shell if it finished normally, 1 if a fatal error of its own (out of memory, file not found) occurs, 2 if the connection to the server went bad and the session was not interactive, and 3 if an error occurred in a script and the variable ON_ERROR_STOP was set.
Well, but what you are looking for from - say - script, that calls
psql to perform single action - is a meaningful exit code. That would
specify whether SQL code returned any errors or not.
This clearly shows, that you can rely only on -c, but others - appear
to be inconsistent. (behave different, depending on how you feed the
input to psql).
--
GJ
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Madison Kelly | 2009-09-16 14:54:30 | Re: I need a Postgres Admin $130K + 20K in NYC Any Ideas? |
| Previous Message | Tom Lane | 2009-09-16 14:31:50 | Re: psql exit code, bug ? |