| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, 158306855 <anderson2013(at)qq(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: [BUG] Re-entering malloc problem when use --enable-nls build postgresql |
| Date: | 2018-05-08 22:04:07 |
| Message-ID: | 10812.1525817047@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Andres Freund <andres(at)anarazel(dot)de> writes:
> Well, the question is if that'd ever have us defer killing the process
> for longer. quickdie is intended to actually die quickly.
Yeah. Though now that we have the postmaster mechanism to wait-five-
seconds-then-SIGKILL, maybe we could rethink that requirement? If we
reimplemented SIGQUIT to work more like SIGTERM, it would surely be
a lot safer. There would be cases where a stuck backend wouldn't
respond and it'd eventually get SIGKILL'd, but in return we'd get rid
of problems like this one.
On balance I'm not sure whether that solution is more or less user-
friendly than the current setup, but for sure it'd be a lot easier
to reason about.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2018-05-08 22:11:05 | Re: [BUG] Re-entering malloc problem when use --enable-nls build postgresql |
| Previous Message | Andres Freund | 2018-05-08 21:40:52 | Re: [BUG] Re-entering malloc problem when use --enable-nls build postgresql |