| From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
|---|---|
| To: | Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-docs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: maximum number of backtrace frames logged by backtrace_functions |
| Date: | 2022-02-07 16:12:58 |
| Message-ID: | b56ce3bf-d308-8dcf-7eaf-e1d3acd021a1@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On 07.02.22 06:29, Fujii Masao wrote:
>>
>> On 2022/02/03 23:48, Tom Lane wrote:
>>> Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> writes:
>>>> How about we issue a message when the backtrace is cut off. Then it's
>>>> immediately visible to the user, instead of hidden away somewhere in
>>>> the
>>>> documentation. Something like this (untested):
>>>
>>> +1 for idea (I didn't test it either).
>>
>> +1. I made this change to the patch and confirmed that it worked fine.
>
> Barring any objection, I will commit the patch.
This change looks good to me. There is also backtrace code in assert.c
that might want the same treatment.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2022-02-07 16:42:49 | Re: maximum number of backtrace frames logged by backtrace_functions |
| Previous Message | Fujii Masao | 2022-02-07 05:29:10 | Re: maximum number of backtrace frames logged by backtrace_functions |