pgsql: Improve what pg_strsignal prints if we haven't gotstrsignal(3). - Mailing list pgsql-committers

From Tom Lane
Subject pgsql: Improve what pg_strsignal prints if we haven't gotstrsignal(3).
Date
Msg-id E1i2ixa-0006Fk-DJ@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
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

Branch
------
REL_12_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/7570df0f3b6d873cd060b3271b5f7b90cbcfb66c

Modified Files
--------------
src/port/pgstrsignal.c | 16 ++++++++--------
1 file changed, 8 insertions(+), 8 deletions(-)


pgsql-committers by date:

Previous
From: Peter Geoghegan
Date:
Subject: pgsql: Remove obsolete nbtree page deletion comment.
Next
From: Tom Lane
Date:
Subject: pgsql: Doc: improve documentation of pg_signal_backend default role.