| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: more backtraces |
| Date: | 2019-12-13 12:26:43 |
| Message-ID: | b43b4c1e-1a52-008f-a188-bd1fbce5aaf8@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2019-12-04 22:34, Tom Lane wrote:
> Andres Freund <andres(at)anarazel(dot)de> writes:
>> It'd be bad if the addition of backtraces for SEGV/BUS suddenly made it
>> harder to attach a debugger and getting useful results.
>
> Yeah. TBH, I'm not sure I want this, at least not in debug builds.
I understand that the SEGV/BUS thing can be a bit scary. We can skip it.
Are people interested in backtraces on abort()? That was asked for in
an earlier thread.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2019-12-13 12:33:21 | Re: Remove configure --disable-float4-byval and --disable-float8-byval |
| Previous Message | Peter Eisentraut | 2019-12-13 12:23:13 | Re: remove support for old Python versions |