Improve what pg_strsignal prints if we haven't got strsignal(3).

Tom Lane <tgl@sss.pgh.pa.us>

Commit: c9bd7f4f2b0fc3b8291914a45cbf2a5270877ee6
Author: Tom Lane <tgl@sss.pgh.pa.us>
Date: 2019-08-27T21:24:47Z
Releases: 13.0
Improve what pg_strsignal prints if we haven't got strsignal(3).

Turns out that returning "unrecognized signal" is confusing.
Make it explicit that the platform lacks any support for signal names.
(At least of the machines in the buildfarm, only HPUX lacks it.)

Back-patch to v12 where we invented this function.

Discussion: https://postgr.es/m/3067.1566870481@sss.pgh.pa.us

Files

PathChange+/−
src/port/pgstrsignal.c modified +8 −8

Discussion