Re: Monitoring postmaster.log

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Walker, Jed S" <Jed_Walker(at)cable(dot)comcast(dot)com>
Cc: pgsql-novice(at)postgresql(dot)org
Subject: Re: Monitoring postmaster.log
Date: 2005-08-06 04:50:45
Message-ID: 15326.1123303845@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-novice

"Walker, Jed S" <Jed_Walker(at)cable(dot)comcast(dot)com> writes:
> I am trying to setup rules to monitor the postmaster.log file, but I
> don't see a way to do it cleanly. I want to monitor for FATAL and
> PANIC, but the problem is that when someon give the wrong password
> logging in, it gives a FATAL error and I don't want to be woken up in
> the middle of the night because of a typo.

Do you actually have a use-case for watching for FATAL errors? I don't
offhand know of any examples where that's important for an admin to pay
attention to. FATAL implies a clean exit of the current session, and
we don't really use that for anything except connection startup rejections
of various sorts (like bad password or too many clients already).

regards, tom lane

In response to

Browse pgsql-novice by date

  From Date Subject
Next Message Google Mike 2005-08-07 14:39:06 PHP App Install Scripts and PostgreSQL
Previous Message Tom Lane 2005-08-06 04:20:24 Re: CREATE CAST question