On 2020-07-10 04:04, Michael Paquier wrote:
On Thu, Jul 09, 2020 at 12:31:38PM -0400, Alvaro Herrera wrote:
On 2020-Jul-09, Daniel Gustafsson wrote:
On 9 Jul 2020, at 11:17, Peter Eisentraut
wrote:
In PG13, we added the ability to add backtraces to the log
output. After some practical exper
On Thu, Jul 09, 2020 at 12:31:38PM -0400, Alvaro Herrera wrote:
> On 2020-Jul-09, Daniel Gustafsson wrote:
>> On 9 Jul 2020, at 11:17, Peter Eisentraut
>> wrote:
>>>
>>> In PG13, we added the ability to add backtraces to the log
>>> output. After some practical experience with it, I think the
>>
On 2020-Jul-09, Daniel Gustafsson wrote:
> > On 9 Jul 2020, at 11:17, Peter Eisentraut
> > 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 pr
> On 9 Jul 2020, at 11:17, Peter Eisentraut
> 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
> fiel
From: Peter Eisentraut
Date: Thu, 9 Jul 2020 11:00:34 +0200
Subject: [PATCH] Log the location field before any backtrace
This order makes more sense because the location is effectively at the
lowest level of the backtrace.
---
src/backend/utils/error/elog.c | 14 +++---
1 file change
