pgsql: Report exit code from external recovery commands properly - Mailing list pgsql-committers

From Peter Eisentraut
Subject pgsql: Report exit code from external recovery commands properly
Date
Msg-id E1Vngr6-0001MC-4K@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Report exit code from external recovery commands properly

When an external recovery command such as restore_command or
archive_cleanup_command fails, report the exit code properly,
distinguishing signals and normal exists, using the existing
wait_result_to_str() facility, instead of just reporting the return
value from system().

Reviewed-by: Peter Geoghegan <pg@heroku.com>

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/fef88b3fdaa3537c64e3d7df9261bc75ece80d3f

Modified Files
--------------
src/backend/access/transam/xlogarchive.c |   11 ++++++-----
1 file changed, 6 insertions(+), 5 deletions(-)


pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: pgsql: Fix crash in assign_collations_walker for EXISTS with empty SELE
Next
From: Bruce Momjian
Date:
Subject: pgsql: libpq: change PQconndefaults() to ignore invalid service files