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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Improve what pg_strsignal prints if we haven't got strsignal(3).
Date: 2019-08-27 21:25:02
Message-ID: E1i2ixa-0006Fk-DJ@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2019-08-27 22:03:24 pgsql: Doc: improve documentation of pg_signal_backend default role.
Previous Message Peter Geoghegan 2019-08-27 21:02:48 pgsql: Remove obsolete nbtree page deletion comment.