Re: maximum number of backtrace frames logged by backtrace_functions

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-18 10:59:17
Message-ID: 5c089e04-1f73-f9f1-b60d-d71d6c33e3f2@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

On 18.02.22 09:24, Fujii Masao wrote:
> Or even backtrace should be logged by write_stderr() so that it's
> written to eventlog if necessary? I just wonder why
> backtrace_symbols_fd() is used only in ExceptionalCondition().

Probably because it was simpler. It would also make sense to convert
the whole thing to use write_stderr() consistently.

In response to

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message David G. Johnston 2022-02-18 14:51:12 Re: Copy Documentation
Previous Message Fujii Masao 2022-02-18 08:24:58 Re: maximum number of backtrace frames logged by backtrace_functions