Re: could not stat promote trigger file leads to shutdown

From: Sergei Kornilov <sk(at)zsrv(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: could not stat promote trigger file leads to shutdown
Date: 2019-11-15 16:49:20
Message-ID: 20865311573836560@vla1-083a2f26e967.qloud-c.yandex.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hello

> Maybe we need a new elevel category for that.
> SYSTEM_WARNING or LOG_WARNING, perhaps?

I think a separate levels for user warnings and system warnings (and errors) would be great for log analytics. Error due to user typo in query is not the same as cache lookup error (for example).

regards, Sergei

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2019-11-15 17:48:18 Re: [PATCH] Implement INSERT SET syntax
Previous Message Tom Lane 2019-11-15 16:31:12 Re: could not stat promote trigger file leads to shutdown