Horton

Re: Printing backtrace of postgres processes

Fujii Masao <masao.fujii@oss.nttdata.com>

View thread View on postgr.es
From: Fujii Masao <masao.fujii@oss.nttdata.com>
To: torikoshia <torikoshia@oss.nttdata.com>, Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2022-01-24T16:36:07Z
Lists: pgsql-hackers 

On 2022/01/24 16:35, torikoshia wrote:
> On 2022-01-14 19:48, Bharath Rupireddy wrote:
>> On Sat, Nov 20, 2021 at 11:50 AM Bharath Rupireddy
>> <bharath.rupireddyforpostgres@gmail.com> wrote:
>>>
>>> On Fri, Nov 19, 2021 at 4:07 PM vignesh C <vignesh21@gmail.com> wrote:
>>> > The Attached v15 patch has the fixes for the same.
>>>
>>> Thanks. The v15 patch LGTM and the cf bot is happy hence marking it as RfC.
>>
>> The patch was not applying because of the recent commit [1]. I took
>> this opportunity and tried a bunch of things without modifying the
>> core logic of the pg_log_backtrace feature that Vignesh has worked on.

I have one question about this feature. When the PID of auxiliary process like archiver is specified, probably the function always reports the same result, doesn't it? Because, for example, the archiver always logs its backtrace in HandlePgArchInterrupts().

Regards,

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

Commits

  1. Perform apply of large transactions by parallel workers.

  2. Enhance pg_log_backend_memory_contexts() for auxiliary processes.

  3. Allow GRANT on pg_log_backend_memory_contexts().

  4. Move Perl test modules to a better namespace

  5. Unify PostgresNode's new() and get_new_node() methods

  6. Add backtrace support for error reporting