| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | vignesh C <vignesh21(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Parallel worker hangs while handling errors. |
| Date: | 2020-09-03 21:07:10 |
| Message-ID: | 20200903210710.GA12611@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2020-Sep-03, Tom Lane wrote:
> As for the question of SIGQUIT handling, I see that postgres.c
> does "PG_SETMASK(&BlockSig)" immediately after applying the sigdelset
> change, so there probably isn't any harm in having the background
> processes do likewise. I wonder though why bgworkers are not
> applying the same policy.
It's quite likely that it's the way it is more by accident than because
I was thinking extremely carefully about signal handling when originally
writing that code. Some parts of that code I was copying from others'
patches, and I could easily have missed a detail like this. (I didn't
"git blame" to verify that these parts are mine, though).
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-09-03 21:07:24 | Re: Maximum password length |
| Previous Message | Alvaro Herrera | 2020-09-03 21:02:06 | Re: default partition and concurrent attach partition |