Re: Remove Windows crash dump support?

On 22.12.2015 18:28, Magnus Hagander wrote:
>
>
> On Tue, Dec 22, 2015 at 3:53 PM, Craig Ringer <craig(at)2ndquadrant(dot)com
> <mailto:craig(at)2ndquadrant(dot)com>> wrote:
>
> On 22 December 2015 at 22:50, Craig Ringer <craig(at)2ndquadrant(dot)com
> <mailto:craig(at)2ndquadrant(dot)com>> wrote:
>
> 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
>
>
> Ahem. 9.1. This is what I get for multi-tasking between writing
> this and packaging an extension for 9.4.
>
>
> In which version(s) of Windows was this improvement added? I think
> that's really the part that matters here, not necessarily which
> version of PostgreSQL.
>
>
> --
> Magnus Hagander
> Me: http://www.hagander.net/
> Work: http://www.redpill-linpro.com/
Hi all!
I think that you can debug crash dump since windbg exists.
Also I think that Postgres on Windows number of instalations is so
tiny because people even today think that it is not so solid as unix
version thats why you think that nobody use your code ;).

Today if my memory serves me right this code can not deal with buffer
overflow. Am i right?
May be we need to add this functionality instead of drop support of it
entirely?

--
Alex Ignatov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company