Re: Add TAP tests for backtrace functionality (was Re: Add test module for verifying backtrace functionality)

On 16.03.24 05:25, Bharath Rupireddy wrote: Postgres has a good amount of code for dealing with backtraces - two GUCs backtrace_functions and backtrace_on_internal_error, errbacktrace; all of which use core function set_backtrace from elog.c. I've not seen this code being tested at all, see code

Add TAP tests for backtrace functionality (was Re: Add test module for verifying backtrace functionality)

On Tue, Feb 20, 2024 at 11:30 AM Bharath Rupireddy wrote: > > On Tue, Feb 13, 2024 at 2:11 AM Bharath Rupireddy > wrote: > > > > Hi, > > > > Postgres has a good amount of code for dealing with backtraces - two > > GUCs backtrace_functions and backtrace_on_internal_error, > > errbacktrace; all of

Re: Add test module for verifying backtrace functionality

On Tue, Feb 13, 2024 at 2:11 AM Bharath Rupireddy wrote: > > Hi, > > Postgres has a good amount of code for dealing with backtraces - two > GUCs backtrace_functions and backtrace_on_internal_error, > errbacktrace; all of which use core function set_backtrace from > elog.c. I've not seen this code

Add test module for verifying backtrace functionality

Hi, Postgres has a good amount of code for dealing with backtraces - two GUCs backtrace_functions and backtrace_on_internal_error, errbacktrace; all of which use core function set_backtrace from elog.c. I've not seen this code being tested at all, see code coverage report -