Re: Allowing nonzero return codes from \quit

From: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
To: Corey Huinker <corey(dot)huinker(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Allowing nonzero return codes from \quit
Date: 2017-01-23 20:43:09
Message-ID: alpine.DEB.2.20.1701232140500.31421@lancre
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Fabien COELHO 2017-01-23 20:57:17 Re: Undefined psql variables
Previous Message Tom Lane 2017-01-23 20:42:22 Re: [COMMITTERS] pgsql: Generate fmgr prototypes automatically