| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Christophe Pettus <xof(at)thebuild(dot)com>, PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: "stuck spinlock" |
| Date: | 2013-12-26 23:18:23 |
| Message-ID: | CA+TgmoatC7fPzy5WN1QBG2m6WddqSC76hdiQYfyqTgZKh1WoKw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Dec 26, 2013 at 11:54 AM, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
> On 12/12/13, 8:45 PM, 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.
>
> Which systems are those?
MacOS X dumps core files into /cores/core.$PID, and at least some
Linux systems seem to dump them into ./core.$PID
I don't know how universal this is. I think a bigger objection to the
SIGSTOP stuff is that a lot of bugs are too real time to ever be
meaningfully caught that way.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2013-12-26 23:25:41 | Re: preserving forensic information when we freeze |
| Previous Message | Joseph Kregloh | 2013-12-26 21:06:59 | Re: pg_upgrade & tablespaces |