On Mon, 2009-09-14 at 09:16 +0900, Itagaki Takahiro wrote:
Another matter is that we use LOG level both cases of important
activity logging and mere performance or query logging. Maybe
we should have used another log level (PERFORMANCE?) for the
latter case, and its priority is less than
On Mon, Sep 14, 2009 at 02:16, Itagaki Takahiro
itagaki.takah...@oss.ntt.co.jp wrote:
Tom Lane t...@sss.pgh.pa.us wrote:
Itagaki Takahiro itagaki.takah...@oss.ntt.co.jp writes:
Can I reorder them to ERROR WARNING LOG ?
No. That was an intentional decision. LOG is for stuff that we
Tom Lane t...@sss.pgh.pa.us wrote:
Itagaki Takahiro itagaki.takah...@oss.ntt.co.jp writes:
Can I reorder them to ERROR WARNING LOG ?
No. That was an intentional decision. LOG is for stuff that we
really want to get logged, in most cases. ERROR is very often not
that interesting, and
LOG messages have higher priority than ERROR and WARNING
in log_min_messages (PANIC FATAL LOG ERROR WARNING) now.
Can I reorder them to ERROR WARNING LOG ? It makes a difference
to per-destination minimum message levels feature that I working on.
LOG messages are often used for performance
Itagaki Takahiro itagaki.takah...@oss.ntt.co.jp writes:
LOG messages have higher priority than ERROR and WARNING
in log_min_messages (PANIC FATAL LOG ERROR WARNING) now.
Can I reorder them to ERROR WARNING LOG ?
No. That was an intentional decision. LOG is for stuff that we
really want
