Re: maximum number of backtrace frames logged by backtrace_functions

From: Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>
To: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(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:42:49
Message-ID: e4ea7dc1-2925-21e1-27b1-44e47b2122bb@oss.nttdata.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

On 2022/02/08 1:12, Peter Eisentraut wrote:
> This change looks good to me.  There is also backtrace code in assert.c that might want the same treatment.

Yeah, that's good idea! The attached patch also adds the same treatment into assert.c.

Regards,

--
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION

Attachment Content-Type Size
backtrace_limit_report_v2.patch text/plain 999 bytes

In response to

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message Erwin Brandstetter 2022-02-08 22:14:05 PL/pgSQL PERFORM WITH query
Previous Message Peter Eisentraut 2022-02-07 16:12:58 Re: maximum number of backtrace frames logged by backtrace_functions