Re: Remove Windows crash dump support?

From: Craig Ringer <craig(at)2ndquadrant(dot)com>
To: Alex Ignatov <a(dot)ignatov(at)postgrespro(dot)ru>
Cc: Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Remove Windows crash dump support?
Date: 2015-12-24 02:14:33
Message-ID: CAMsr+YEksrH7tPXbMh+TRg5zOcZuHrv0HhUUEbhEf2x=3xoM=g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 22 December 2015 at 23:48, Alex Ignatov <a(dot)ignatov(at)postgrespro(dot)ru> wrote:

> I think that you can debug crash dump since windbg exists.
>

Nobody in their right mind uses windbg though. Visual Studio is really
where it's at and the Express versions make it much more practical.

You can't even install Debugging Tools for Windows and Windbg standalone
anymore.

> 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 ;).
>

I disagree. Windows Pg users are often at bigger companies and don't talk
about PostgreSQL as much. Often for fear of reprisals from other database
vendors they have ongoing relationships with. At least that's been my
experience and I'm sure EDB folks will concur.

> Today if my memory serves me right this code can not deal with buffer
> overflow. Am i right?
>

Stack overflow?

No, it can't. The stack has to be somewhat sane.

> May be we need to add this functionality instead of drop support of it
> entirely
>

Why? I've never seen any sign anybody has used it, ever.

--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2015-12-24 02:15:49 Re: HINTing on UPDATE foo SET foo.bar = ..;
Previous Message Michael Paquier 2015-12-24 02:14:09 Re: COPY FREEZE and PD_ALL_VISIBLE