| From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
|---|---|
| To: | Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, Andres Freund <andres(at)anarazel(dot)de>, Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: PATCH: backtraces for error messages |
| Date: | 2018-06-22 00:24:45 |
| Message-ID: | CAMsr+YGgmnqzPZoXNmcoXe-1itqLFeW=4S+3Md0GJ6ew7nnH4Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu., 21 Jun. 2018, 19:26 Pavan Deolasee, <pavan(dot)deolasee(at)gmail(dot)com>
wrote:
>
>
> 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].
>
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.
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2018-06-22 00:38:19 | Re: Sample values for pg_stat_statements |
| Previous Message | Jeff Davis | 2018-06-21 23:57:05 | Re: Spilling hashed SetOps and aggregates to disk |