Re: [HACKERS] Allowing nonzero return codes from \quit - Mailing list pgsql-hackers

From Fabien COELHO
Subject Re: [HACKERS] Allowing nonzero return codes from \quit
Date
Msg-id alpine.DEB.2.20.1701232140500.31421@lancre
Whole thread Raw
In response to Re: [HACKERS] Allowing nonzero return codes from \quit  (Corey Huinker <corey.huinker@gmail.com>)
Responses Re: [HACKERS] Allowing nonzero return codes from \quit  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
>> As \q does not currently have an argument, this seems an easy and
>> reasonnable extension.
>>
>> However, currently there are 4 existing exit status for psql: 0 (ok), 1
>> (fatal error), 2 (connection error), 3 (script error...). +128 status are
>> also already used when killing a psql process.
>
> I didn't think about it too much, but I don't see why a user couldn't set
> one of those error codes.
> I did, however, think that any attempt to set an exit_code outside of
> [0,127] would itself be an error, resulting in an exit code of 3.

Hmmm. Maybe it should let the user shoots its own foot if desired, just a 
reminder in the doc of a possible interference with existing codes would 
be enough?

-- 
Fabien.



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] [COMMITTERS] pgsql: Generate fmgr prototypes automatically
Next
From: Fabien COELHO
Date:
Subject: Re: [HACKERS] Undefined psql variables