public inbox for [email protected]
help / color / mirror / Atom feedFrom: Peter Eisentraut <[email protected]>
To: Tom Lane <[email protected]>
To: Robert Haas <[email protected]>
Cc: Andres Freund <[email protected]>
Cc: pgsql-hackers <[email protected]>
Subject: Re: backtrace_on_internal_error
Date: Sat, 30 Dec 2023 12:11:59 +0100
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<CA+TgmoYqwk1rEaPurzfOwB5WSfo5x7NbzLVbQNJOeS210nAwdg@mail.gmail.com>
<[email protected]>
On 19.12.23 17:29, Tom Lane wrote:
> IMO, we aren't really going to get a massive payoff from this with
> the current backtrace output; it's just not detailed enough. It's
> better than nothing certainly, but to really move the goalposts
> we'd need something approaching gdb's "bt full" output. I wonder
> if it'd be sane to try to auto-invoke gdb. That's just blue sky
> for now, though. In the meantime, I agree with the proposal as it
> stands (that is, auto-backtrace on any XX000 error). We'll soon find
> out whether it's useless, or needs more detail to be really helpful,
> or is just right as it is. Once we have some practical experience
> with it, we can course-correct as needed.
Based on this, I have committed my original patch.
view thread (14+ messages)
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected]
Subject: Re: backtrace_on_internal_error
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox