On Fri, Jun 7, 2024 at 4:28 PM Alvaro Herrera <alvhe...@alvh.no-ip.org> wrote: > > On 2024-Jun-07, jian he wrote: > > > so when it actually happens, it cannot quickly locate which function > > where the error has happened. > > maybe under certain conditions (e.g. certain build type or certain > > log_min_messages), > > we can also print out the function name by using gcc __func__. > > That information is already in the error data, so you don't need it in > the message text. You can change your log_error_verbosity if you want > it to show up in the log; in psql you can use \errverbose to have it > shown to you after the error is thrown, or you can use > \pset VERBOSITY verbose > to have it printed for every error message. Tools other than psql would > need their own specific ways to display those. >
Thanks for pointing this out.
