Re: PATCH: backtraces for error messages - Mailing list pgsql-hackers

From Pavan Deolasee
Subject Re: PATCH: backtraces for error messages
Date
Msg-id CABOikdP+bj-KVq1nzOQthWbu1EVE2=HEYW_BBh0isd_O7MQE-Q@mail.gmail.com
Whole thread Raw
In response to Re: PATCH: backtraces for error messages  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers


On Fri, Jun 22, 2018 at 6:18 AM, Andres Freund <andres@anarazel.de> wrote:
On 2018-06-22 08:24:45 +0800, Craig Ringer wrote:
>
>
> Huge +1 from me on being able to selectively manage logging on a
> module/subsystem, file, or line level.
>
> I don't think I saw the post.
>
> Such a thing would obviously make built in backtrace support much more
> useful.

I strongly suggest keeping these as separate as possible. Either is
useful without the other, and both are nontrivial. Tackling them
together imo makes it much more likely to get nowhere.


Sorry, I did not mean to mix up two patches. I brought it up just in case it provides another idea about when and how to log the backtrace. So yeah, let's discuss that patch separately.

Thanks,
Pavan 

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

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: PANIC during crash recovery of a recently promoted standby
Next
From: Jeevan Chalke
Date:
Subject: Re: Server crashed with TRAP: FailedAssertion("!(parallel_workers >0)" when partitionwise_aggregate true.