pgsql: Make error handling in parallel pg_upgrade less bogus.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Make error handling in parallel pg_upgrade less bogus.
Date: 2018-12-16 19:52:06
Message-ID: E1gYcSM-0008Ov-NI@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Make error handling in parallel pg_upgrade less bogus.

reap_child() basically ignored the possibility of either an error in
waitpid() itself or a child process failure on signal. We don't really
need to do more than report and crash hard, but proceeding as though
nothing is wrong is definitely Not Acceptable. The error report for
nonzero child exit status was pretty off-point, as well.

Noted while fooling around with child-process failure detection
logic elsewhere. It's been like this a long time, so back-patch to
all supported branches.

Branch
------
REL_11_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/b054498c74c3630348b9a35f7f4c6dc90e204643

Modified Files
--------------
src/bin/pg_upgrade/parallel.c | 17 ++++++++---------
1 file changed, 8 insertions(+), 9 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2018-12-17 00:39:07 pgsql: Modernize our code for looking up descriptive strings for Unix s
Previous Message Tom Lane 2018-12-14 17:53:02 pgsql: Make pg_statistic and related code account more honestly for col