On 2019-Dec-15, Tom Lane wrote:
> Robert Haas <robertmhaas@gmail.com> writes:
> > Being able to get debugging information from
> > failures that happen on those installations that enables us to fix
> > things without having to go through a time-consuming process of
> > guesswork and attempted reproduction is really valuable. A stack trace
> > can turn a lengthy nightmare into a quick fix.
>
> I think you are supposing that these traces will be as useful as gdb
> traces. They won't. In particular, where a gdb trace will almost
> always localize the problem to a line of C code, with these you're
> quite lucky if you can even localize to a specific function.
That's already been my experience :-(
> I think that the most useful next steps would involve trying to get
> better printouts from the cases this code already traps,
+1
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services