| From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Christophe Pettus <xof(at)thebuild(dot)com>, PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: "stuck spinlock" |
| Date: | 2013-12-27 07:51:19 |
| Message-ID: | 20131227075119.GA17584@alap2.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2013-12-12 20:45:17 -0500, Tom Lane wrote:
> Memo to hackers: I think the SIGSTOP stuff is rather obsolete now that
> most systems dump core files with process IDs embedded in the names.
> What would be more useful today is an option to send SIGABRT, or some
> other signal that would force core dumps. Thoughts?
Although I didn't know of the option, I thought having it would be
useful before. It allows you to inspect the memory of the individual
backends while they are still alive - which allows gdb to call
functions. Which surely is helpful when debugging some issues.
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2013-12-27 07:54:53 | Re: INSERT...ON DUPLICATE KEY LOCK FOR UPDATE |
| Previous Message | Martijn van Oosterhout | 2013-12-27 07:47:57 | Re: "stuck spinlock" |