Magnus Hagander wrote:
> >> Seems like we need something like WARNING that doesn't cause the process
> >> to die, but more alarming like ERROR/FATAL/PANIC. Or maybe just adding a
> >> hint to the warning will do. How about
> >>
> >> WARNING: ?invalid record length at 0/4005330
> >> HINT: An invalid record was streamed from master. That can be a sign of
> >> corruption in the master, or inconsistency between master and standby
> >> state. The record will be re-fetched, but that is unlikely to fix the
> >> problem. You may have to restore standby from base backup.
> >
> > I am thinking about log monitoring tools like Nagios. ?I am afraid
> > they are never going to pick up something tagged WARNING, no matter
>
> If they are properly configured, I imagine they would. And if they're
> not, well, there's not much for us to do.
What does that mean?
> (What would be more usful then would be to separate "user-warnings"
> like warnings about cast from actual system-warnings like this, but
> that's a whole different story)
>
> > what the wording is. ?Crazy idea, but can we force a fatal error line
> > into the logs with something like "WARNING ...\nFATAL: ...".
>
> That's way too crazy :P And btw, randomly sticking newlines into that
> will mess up *most* log displayers and I bet a lot of the log
> monitoring tools as well...
Yeah, it would mess up CSV log output, for example?
-- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB
http://enterprisedb.com
+ None of us is going to be here forever. +
