From: | Andrey Borodin <x4mmm(at)yandex-team(dot)ru> |
---|---|
To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: more backtraces |
Date: | 2025-02-01 17:29:06 |
Message-ID: | 2A31C2D3-35A1-4389-A9D4-3717BB51AE28@yandex-team.ru |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> On 5 Dec 2019, at 00:45, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> wrote:
>
> <0001-Print-backtrace-on-SIGABRT-SIGBUS-SIGSEGV.patch>
Hello!
I find this patch very useful when hacking, so let's have a rebased version in archives.
And +1 for the feature. The backtrace could help collect diagnostics in case of production incidents.
Thanks!
Best regards, Andrey Borodin.
Attachment | Content-Type | Size |
---|---|---|
v2-0001-Print-backtrace-on-SIGABRT-SIGBUS-SIGSEGV.patch | application/octet-stream | 3.2 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Lars Kanis | 2025-02-01 19:22:32 | [PATCH] Fix build on MINGW on ARM64 |
Previous Message | Srinath Reddy | 2025-02-01 16:06:29 | Re: Non-text mode for pg_dumpall |