Search Postgresql Archives

Re: psql exit code, bug ?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



2009/9/16 Tom Lane <tgl@xxxxxxxxxxxxx>:
> =?UTF-8?Q?Grzegorz_Ja=C5=9Bkiewicz?= <gryzman@xxxxxxxxx> 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

-- 
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux