On 2022/02/03 23:48, Tom Lane wrote:
Peter Eisentraut writes:
How about we issue a message when the backtrace is cut off. Then it's
immediately visible to the user, instead of hidden away somewhere in the
documentation. Something like this (untested):
+1 for idea (I didn't test it either)
Peter Eisentraut writes:
> How about we issue a message when the backtrace is cut off. Then it's
> immediately visible to the user, instead of hidden away somewhere in the
> documentation. Something like this (untested):
+1 for idea (I didn't test it either). Is "nframes" useful enough to
in
On 03.02.22 06:33, Fujii Masao wrote:
I encountered the "more than 100 backtrace frames" case when
investigating the bug of pg_log_query_plan() patch [1]. Since the
function that the patch added can be called repeatedly during call to
that function, the backtrace became larger than 100. I think
