On Tue, Nov 16, 2021 at 1:12 AM Justin Pryzby <pry...@telsasoft.com> wrote: > > 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.
+1 for pg_log_backtrace(). Regards, Bharath Rupireddy.
