Re: Remove Windows crash dump support?

From: Andres Freund <andres(at)anarazel(dot)de>
To: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
Cc: Craig Ringer <craig(at)2ndquadrant(dot)com>, Dave Page <dpage(at)pgadmin(dot)org>, Alex Ignatov <a(dot)ignatov(at)postgrespro(dot)ru>, Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Remove Windows crash dump support?
Date: 2016-01-04 08:17:05
Message-ID: 20160104081705.lvv3n4qqnelsyrxd@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2016-01-04 16:39:22 +0900, Michael Paquier wrote:
> So I think that it is still useful for debugging code
> paths running custom code, even if we consider Postgres as rock-solid
> on Windows.

Given the state of e.g. the socket using code for windows I personally
certainly don't consider it rock solid.

Either way, since there were a few people interested in keeping the
support, and nobody really had any arguments besids "seems unused" for
removing it, this seems like a pretty clear cut case.

Andres

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2016-01-04 08:24:46 Re: count_nulls(VARIADIC "any")
Previous Message Simon Riggs 2016-01-04 08:11:10 Re: Keyword classifications