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

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Craig Ringer <craig(at)2ndquadrant(dot)com>, "Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Haribabu Kommi <kommi(dot)haribabu(at)gmail(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-11-11 00:02:01
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On Sun, Nov 10, 2019 at 11:24:34AM -0500, Tom Lane wrote:
> I feel the pain on this --- indirect dependencies are not well reported
> on any platform that I deal with :-(. Still, I'm having a hard time
> convincing myself that this patch is a good idea. It seems very likely
> that it will break some startup scenarios, and the incremental benefit
> in error reporting seems marginal.

Thanks for your input, Tom. This matches with my opinion about this
thread and this patch.

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Euler Taveira 2019-11-11 01:01:04 Re: psql \d for wide tables / pattern for individual columns
Previous Message Alexander Korotkov 2019-11-10 23:42:42 Re: Connections hang indefinitely while taking a gin index's LWLock buffer_content lock(PG10.7)