Re: parallel.c oblivion of worker-startup failures
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Amit Kapila <amit.kapila16@gmail.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2017-09-18T16:30:44Z
Lists: pgsql-hackers
Amit Kapila <amit.kapila16@gmail.com> writes: > Attached patch fixes these problems. Hmm, this patch adds a kill(notify_pid) after one call to ForgetBackgroundWorker, but the postmaster has several more such calls. Shouldn't they all notify the notify_pid? Should we move that functionality into ForgetBackgroundWorker itself, so we can't forget it again? regards, tom lane
Commits
-
Report an ERROR if a parallel worker fails to start properly.
- 2843c01a56eb 9.6.7 landed
- 383e4268ff8c 10.2 landed
- 2badb5afb89c 11.0 landed
-
Report failure to start a background worker.
- facd94e72f27 9.4.16 landed
- 0426a77ce465 9.5.11 landed
- b75644066091 9.6.7 landed
- a8ef4e81e6f2 10.2 landed
- 28724fd90d2f 11.0 landed