Re: [bug fix] Produce a crash dump before main() on Windows

From: Craig Ringer <craig(at)2ndquadrant(dot)com>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: "Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [bug fix] Produce a crash dump before main() on Windows
Date: 2018-02-20 14:25:02
Message-ID: CAMsr+YHc5jzkEFJ_ZTs7VjocVNpUQSRE15TiWRsSF7pK0Y2AKQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 20 February 2018 at 22:18, Craig Ringer <craig(at)2ndquadrant(dot)com> wrote:

> So I'm all for just removing that.
>

... but just to be clear, about -1000 on backpatching any such thing. At
most, a new GUC that defaults to the current behaviour. But I think it's
pretty niche really.

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Matheus de Oliveira 2018-02-20 14:34:47 [PATCH] btree_gin, add support for uuid, bool, name, bpchar and anyrange types
Previous Message Craig Ringer 2018-02-20 14:18:20 Re: [bug fix] Produce a crash dump before main() on Windows