| From: | Francisco Olarte <folarte(at)peoplecall(dot)com> |
|---|---|
| To: | Wallace Baggaley <wally(dot)baggaley(at)gmail(dot)com> |
| Cc: | Merlin Moncure <mmoncure(at)gmail(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #15021: Postgres crashes unexpectedly |
| Date: | 2018-01-20 09:51:10 |
| Message-ID: | CA+bJJbyS+R0aN9khNWjT2NoeUprUaH77Er4bJQtP3--pP4PxSQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Sat, Jan 20, 2018 at 1:32 AM, Wallace Baggaley
<wally(dot)baggaley(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2018-01-21 00:56:30 | Re: BUG #15021: Postgres crashes unexpectedly |
| Previous Message | Amit Kapila | 2018-01-20 06:15:27 | Re: BUG #15001: planner cann't distinguish composite index? |