Re: Log the location field before any backtrace

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Log the location field before any backtrace
Date: 2020-07-09 11:25:43
Message-ID: C8394FF2-0E6D-49D0-8DEE-6155AA8D7065@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 9 Jul 2020, at 11:17, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> wrote:
>
> In PG13, we added the ability to add backtraces to the log output. After some practical experience with it, I think the order in which the BACKTRACE and the LOCATION fields are printed is wrong. I propose we put the LOCATION field before the BACKTRACE field, not after. This makes more sense because the location is effectively at the lowest level of the backtrace.

Makes sense, +1

cheers ./daniel

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Daniel Gustafsson 2020-07-09 11:38:45 Re: Allow an alias to be attached directly to a JOIN ... USING
Previous Message Amit Kapila 2020-07-09 11:15:22 Re: PATCH: logical_work_mem and logical streaming of large in-progress transactions