| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | David Pacheco <dap(at)joyent(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: [GENERAL] postmaster deadlock while logging after syslogger exited |
| Date: | 2017-11-20 19:17:33 |
| Message-ID: | 20171120191733.ac34edgl5x6adrbb@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi,
On 2017-11-20 11:12:08 -0800, David Pacheco wrote:
> > > This is a critical point. As far as I can tell, all that's necessary
> > > for this deadlock to occur is:
> > >
> > > - the syslogger is unable to make forward progress (e.g., because it
> > > segfaulted)
> >
> > This specific case I don't care that much about, but ...
> I understand if the community isn't interested in fixing this case if other
> users aren't seeing it much, but surely it's still a bug that this unusual
> case can result in a deadlock?
I care about the deadlock issue if triggered by out of memory
cases. That's something that can be expected during operation. Being
fully resistant against segfaults in arbitrary places however is not
unlikely to introduce more bugs than cases where it saves the day.
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vick Khera | 2017-11-20 19:34:45 | Re: To all who wish to unsubscribe |
| Previous Message | David Pacheco | 2017-11-20 19:12:08 | Re: [GENERAL] postmaster deadlock while logging after syslogger exited |