Re: BUG #15021: Postgres crashes unexpectedly - Mailing list pgsql-bugs

From Francisco Olarte
Subject Re: BUG #15021: Postgres crashes unexpectedly
Date
Msg-id CA+bJJbyS+R0aN9khNWjT2NoeUprUaH77Er4bJQtP3--pP4PxSQ@mail.gmail.com
Whole thread Raw
In response to Re: BUG #15021: Postgres crashes unexpectedly  (Wallace Baggaley <wally.baggaley@gmail.com>)
List pgsql-bugs
On Sat, Jan 20, 2018 at 1:32 AM, Wallace Baggaley
<wally.baggaley@gmail.com> wrote:
> This was pulled from kibana/elasticsearch, so logs with the same millisecond
> log may be out-of-order. Otherwise should be in order.

They seem to be in DESCENDING time order. This is used by a lot of
things ( like the gmail web MUA I'm using now ), as it can be prettier
to show /easier to look at the last event in a web form / ... but due
to the way people are usually taught to read it makes reading it for
diagnostic purpose extremely difficult / annoying.

Francisco Olarte


pgsql-bugs by date:

Previous
From: Amit Kapila
Date:
Subject: Re: BUG #15001: planner cann't distinguish composite index?
Next
From: Tomas Vondra
Date:
Subject: Re: BUG #15021: Postgres crashes unexpectedly