pgsql: Report exit code from external recovery commands properly

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Report exit code from external recovery commands properly
Date: 2013-12-03 03:41:00
Message-ID: E1Vngr6-0001MC-4K@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)heroku(dot)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(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Noah Misch 2013-12-03 05:47:07 Re: pgsql: Fix a couple of bugs in MultiXactId freezing
Previous Message Tom Lane 2013-12-03 01:29:40 pgsql: Fix crash in assign_collations_walker for EXISTS with empty SELE