Re: PATCH: backtraces for error messages

On Thu, Jun 21, 2018 at 11:02 AM, Michael Paquier <michael(at)paquier(dot)xyz>
wrote:

> On Thu, Jun 21, 2018 at 12:35:10PM +0800, Craig Ringer wrote:
> > I wrote it because I got sick of Assert(false) debugging, and I was
> chasing
> > down some "ERROR: 08P01: insufficient data left in message" errors.
> Then I
> > got kind of caught up in it... you know how it is.
>
> Yes, I know that feeling! I have been using as well the Assert(false)
> and the upgrade-to-PANIC tricks a couple of times, so being able to get
> more easily backtraces would be really nice.
>
>
Sometime back I'd suggested an idea to be able to dynamically manage log
levels for elog messages [1]. That did not invoke much response, but I
still believe some such facility will be very useful for debugging
production systems. Now I concede that the POC patch that I sent is
horribly written and has a bad UI, but those can be improved if there is
interest. Given the lack of response, I suspect there is enough interest in
the feature though.

Thanks,
Pavan

[1]
https://www.postgresql.org/message-id/CABOikdMvx_Kr_b4ELhJEoeGcLTZKrDma%2BfPZpoZVdpL7Zc0bVw%40mail.gmail.com

--
Pavan Deolasee http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services