pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Justin Pryzby <pryzby@telsasoft.com>
To: vignesh C <vignesh21@gmail.com>
Cc: Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Andres Freund <andres@anarazel.de>
Cc: Craig Ringer <craig.ringer@enterprisedb.com>
Cc: Robert Haas <robertmhaas@gmail.com>
Cc: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Cc: pgsql-hackers@lists.postgresql.org
Subject: Re: Printing backtrace of postgres processes
Date: Wed, 5 May 2021 21:13:24 -0500
Message-ID: <20210506021324.GD27406@telsasoft.com> (raw)
In-Reply-To: <CALDaNm33u1REpYEXtnmTNNN=pfeZDOOWyDSSi+VjcRukxMewTA@mail.gmail.com>
References: <CALDaNm1uWKn8KGD0q8HqCPhxSUDKWCEW55aidOiJwd+vfaB+gg@mail.gmail.com>
	<CALj2ACXfXefmdUWiF0twoYEfgJ6Xk4saXctoYyzXtzkjizCdBw@mail.gmail.com>
	<CALDaNm0aEUNLZeiDAXvPsgm4nFUjUhtfeztGofmVJU--irSD8Q@mail.gmail.com>
	<CALj2ACXybys_tzWeatb9htVTuxKp29VErc6iJQYJBbdBZXv2fg@mail.gmail.com>
	<CALj2ACUhgagr-nLcte2+61khpO6uxvERvZA28hQpxtTzbz3U2g@mail.gmail.com>
	<CALDaNm3HHMxUpYYbUFM3=RYBYZjQGgnULxdDrqwaH=DovuYMSQ@mail.gmail.com>
	<3886673.1612337426@sss.pgh.pa.us>
	<CALDaNm0aKEpGXf-7RN87B_DXZ8XTnuMGOA5NR6f2b532AhMAyw@mail.gmail.com>
	<CALj2ACWeYdLRM5OF_YaRROmdJky-ip6dhCToU8SCjXHn7hUYzA@mail.gmail.com>
	<CALDaNm33u1REpYEXtnmTNNN=pfeZDOOWyDSSi+VjcRukxMewTA@mail.gmail.com>

Here's a cleaned-up copy of the doc text.

Send a request to the backend with the specified process ID to log its backtrace.
The backtrace will be logged at message level <literal>LOG</literal>.
It will appear in the server log based on the log configuration set
(See <xref linkend="runtime-config-logging"/> for more information),
but will not be sent to the client regardless of
<xref linkend="guc-client-min-messages"/>.
A backtrace will identify where exactly the backend process is currently
executing. This may be useful to developers to diagnose stuck
processes and other problems. This feature is
not supported for the postmaster, logger, or statistics collector process. This
feature will be available if PostgreSQL was built
with the ability to capture backtracee.  If not available, the function will
return false and show a WARNING.
Only superusers can request backends to log their backtrace.

> - * this and related functions are not inlined.
> + * this and related functions are not inlined. If edata pointer is valid
> + * backtrace information will set in edata.

will *be* set

-- 
Justin





view thread (135+ messages)  latest in thread

Message-ID: <20210506021324.GD27406@telsasoft.com>
Permalink:  ../20210506021324.GD27406@telsasoft.com/
Also on:    postgresql.org/message-id/20210506021324.GD27406@telsasoft.com

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: pryzby@telsasoft.com, vignesh21@gmail.com, bharath.rupireddyforpostgres@gmail.com, tgl@sss.pgh.pa.us, andres@anarazel.de, craig.ringer@enterprisedb.com, robertmhaas@gmail.com, peter.eisentraut@enterprisedb.com, pgsql-hackers@lists.postgresql.org
  Subject: Re: Printing backtrace of postgres processes
  In-Reply-To: <20210506021324.GD27406@telsasoft.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox