From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
---|---|
To: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Remove Windows crash dump support? |
Date: | 2015-12-22 14:50:49 |
Message-ID: | CAMsr+YGyhTE9BhdKdB37GLqg2EcUxXOe_UXS8=U0cqn8g99egg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi all
Back in 2010 I submitted a small feature to allow the creation of minidumps
when backends crashed; see commit dcb09b595f88a3bca6097a6acc17bf2ec935d55f .
At the time Windows lacked useful support for postmortem debugging and
crash-dump management in the operating system its self, especially for
applications running as services. That has since improved considerably.
The feature was also included in 9.4, which I think was the PostgreSQL
release that was really rock solid on Windows. Consequently it's never
served the purpose I wrote it for, a way to make it easy to get crash data
from end users into the hands of a developer without needing to
remote-debug the users' system.
It's practically dead code and we might as well remove it unless there's
someone out there using it who's keeping quiet about it.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Craig Ringer | 2015-12-22 14:53:14 | Re: Remove Windows crash dump support? |
Previous Message | Noah Misch | 2015-12-22 14:49:50 | Re: PATCH: Split stats file per database WAS: autovacuum stress-testing our system |