Re: psql exit code, bug ? - Mailing list pgsql-general

From Grzegorz Jaśkiewicz
Subject Re: psql exit code, bug ?
Date
Msg-id 2f4958ff0909160735h6b160354o8cbb6c2e93e52590@mail.gmail.com
Whole thread Raw
In response to Re: psql exit code, bug ?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
2009/9/16 Tom Lane <tgl@sss.pgh.pa.us>:
> =?UTF-8?Q?Grzegorz_Ja=C5=9Bkiewicz?= <gryzman@gmail.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
scriptand 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

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: psql exit code, bug ?
Next
From: Madison Kelly
Date:
Subject: Re: I need a Postgres Admin $130K + 20K in NYC Any Ideas?