Horton

Re: Printing backtrace of postgres processes

torikoshia <torikoshia@oss.nttdata.com>

View thread View on postgr.es
From: torikoshia <torikoshia@oss.nttdata.com>
To: Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
Cc: vignesh C <vignesh21@gmail.com>, Andres Freund <andres@anarazel.de>, Tom Lane <tgl@sss.pgh.pa.us>, Craig Ringer <craig.ringer@enterprisedb.com>, Robert Haas <robertmhaas@gmail.com>, Peter Eisentraut <peter.eisentraut@enterprisedb.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2021-03-05T09:47:52Z
Lists: pgsql-hackers 
On 2021-03-04 21:55, Bharath Rupireddy wrote:
> On Mon, Mar 1, 2021 at 10:43 AM torikoshia <torikoshia@oss.nttdata.com> 
> wrote:
>> Since the current patch use BackendPidGetProc(), it does not
>> support this feature not only postmaster, logging, and
>> statistics but also checkpointer, background writer, and
>> walwriter.
>> 
>> And when I specify pid of these PostgreSQL processes, it
>> says "PID xxxx is not a PostgreSQL server process".
>> 
>> I think it may confuse users, so it might be worth
>> changing messages for those PostgreSQL processes.
>> AuxiliaryPidGetProc() may help to do it.
> 
> Exactly this was the doubt I got when I initially reviewed this patch.
> And I felt it should be discussed in a separate thread, you may want
> to update your thoughts there [1].
> 
> [1] -
> https://www.postgresql.org/message-id/CALj2ACW7Rr-R7mBcBQiXWPp%3DJV5chajjTdudLiF5YcpW-BmHhg%40mail.gmail.com

Thanks!
I'm going to join the discussion there.


Regards,

--
Atsushi Torikoshi
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