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

From: Alvaro Herrera from 2ndQuadrant <alvherre(at)alvh(dot)no-ip(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com>, 'Amit Kapila' <amit(dot)kapila16(at)gmail(dot)com>, Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, Robert Haas <robertmhaas(at)gmail(dot)com>, Craig Ringer <craig(at)2ndquadrant(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [bug fix] Produce a crash dump before main() on Windows
Date: 2019-09-06 13:45:42
Message-ID: 20190906134542.GA7762@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2019-Sep-05, Tom Lane wrote:

> Alvaro Herrera from 2ndQuadrant <alvherre(at)alvh(dot)no-ip(dot)org> writes:
> > Tsunakawa-san, there's been some discussion downthread. Could you
> > please submit an updated version of the patch? I would like to get it
> > pushed before beta4 next week, if possible.
>
> [ confused... ] I haven't been paying attention to this thread,
> but is it really something we'd push into v12 at this point?

Well, IMV this is a backpatchable, localized bug fix. I was thinking it
would be better to get some coverage in the upcoming beta, where it can
be fixed without too much harm if there are problems with it, before
backpatching further. But if even that is considered too dangerous, I
guess we could put it in master for a while, and consider a backpatch
later.

--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Yuli Khodorkovskiy 2019-09-06 13:51:17 Re: add a MAC check for TRUNCATE
Previous Message Asim R P 2019-09-06 13:22:51 Re: Fault injection framework