Date: Mon, 15 Nov 2021 13:42:51 -0600
From: Justin Pryzby <pryzby@telsasoft.com>
To: vignesh C <vignesh21@gmail.com>
Cc: Dilip Kumar <dilipbalaut@gmail.com>,
	Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>,
	Daniel Gustafsson <daniel@yesql.se>,
	Robert Haas <robertmhaas@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>,
	Andres Freund <andres@anarazel.de>,
	Craig Ringer <craig.ringer@enterprisedb.com>,
	Peter Eisentraut <peter.eisentraut@enterprisedb.com>,
	pgsql-hackers@lists.postgresql.org
Subject: Re: Printing backtrace of postgres processes
Message-ID: <20211115194251.GP17618@telsasoft.com>
References: 
 <CALDaNm3MGVP_WK1Uuf=BiAJ9PeVOfciwLy0mrFA1JNbRp99VOQ@mail.gmail.com>
 <CALj2ACUbq3Pbm427BOfzj2Je3KQ9Ys-uyXn5SBENYzOkzesvmQ@mail.gmail.com>
 <CALDaNm3HTxjppsN1fe7kJGb-15uO4GN4PvdPu8zaEHtYqQLFhQ@mail.gmail.com>
 <CALj2ACUFD-CW4n+Piu8pq9TYs1keAz_ga5C-6ZbjWrUGZ1GCMQ@mail.gmail.com>
 <CALj2ACW00oW1s_NajhaA8f+8jyHCfBRfCD74y+vKXoDZPC2oWw@mail.gmail.com>
 <CALDaNm1SjDNaH=sHyD5emm8+F9f-A4x12Xxare0bJ_9iPmexLA@mail.gmail.com>
 <CALj2ACXLiMFGvGhcL7SsVUX+R1NyyoJ1WR52SNrzFiEq-MY5Xg@mail.gmail.com>
 <CALDaNm3m5hVB9CicU5-VzLgT6dvFYYJNyU=8U7OA9+2Wx6=Gqg@mail.gmail.com>
 <CAFiTN-ueXOUOfZwuCd27komxXioaaN5sLatceOePkO1nZYUzAg@mail.gmail.com>
 <CALDaNm0-UmyWijsiyOGt0JERdS8U_aVpQdoW1UC1g3wZcfwYoA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: 
 <CALDaNm0-UmyWijsiyOGt0JERdS8U_aVpQdoW1UC1g3wZcfwYoA@mail.gmail.com>
User-Agent: Mutt/1.9.4 (2018-02-28)
Archived-At: 
 <https://www.postgresql.org/message-id/20211115194251.GP17618%40telsasoft.com>
Precedence: bulk

On Mon, Nov 15, 2021 at 09:12:49PM +0530, vignesh C wrote:
> The idea here is to implement & expose pg_print_backtrace function, internally

This patch is closely related to this one
https://commitfest.postgresql.org/35/3142/
| Logging plan of the currently running query

I suggest to review that patch and make sure there's nothing you could borrow.

My only comment for now is that maybe the function name should be
pg_log_backtrace() rather than pg_print_backtrace(), since it doesn't actually
"print" the backtrace, but rather request the other backend to log its
backtrace.

Did you see that the windows build failed ?
https://ci.appveyor.com/project/postgresql-cfbot/postgresql/build/1.0.153557

I think you'll need to create an "alternate" output like
src/test/regress/expected/misc_functions_1.out

It's possible that's best done by creating a totally new .sql and .out files
added to src/test/regress/parallel_schedule - because otherwise, you'd have to
duplicate the existing 300 lines of misc_fuctions.out.

-- 
Justin