| From: | Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
| Cc: | pgsql-docs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: maximum number of backtrace frames logged by backtrace_functions |
| Date: | 2022-02-07 05:29:10 |
| Message-ID: | 33675df8-60e1-7da6-8995-3743668fd682@oss.nttdata.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On 2022/02/04 9:48, 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.
Regards,
--
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2022-02-07 16:12:58 | Re: maximum number of backtrace frames logged by backtrace_functions |
| Previous Message | Jonathan S. Katz | 2022-02-07 02:29:56 | Re: documentation on HOT |