From: | Kevin Brannen <KBrannen(at)efji(dot)com> |
---|---|
To: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | RE: Patterns to look for in the PostgreSQL server log |
Date: | 2020-03-11 13:14:51 |
Message-ID: | MW3PR19MB4252DC28BBB7B77AACF25273A4FC0@MW3PR19MB4252.namprd19.prod.outlook.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
>From: Mageshwaran Janarthanam <mageshwaran(dot)janarthanam(at)gmail(dot)com>
>
>Hi Team...I am trying to setup some monitoring over the PostgreSQL server log. I am not clear which error I should be most concerned about. Could you please share your thoughts on what pattern I should search in the log file?
I'd treat it like any other log and apply negative filters; i.e. filter out
things that aren't a problem, which leaves things you do care about and
anything unexpected (which might cause you to add another filter to remove
it for next time if you find it's not really a problem).
Adrian is giving good advice too. Understand the log levels and set your config
appropriately for your situation and comfort level.
This e-mail transmission, and any documents, files or previous e-mail messages attached to it, may contain confidential information. If you are not the intended recipient, or a person responsible for delivering it to the intended recipient, you are hereby notified that any disclosure, distribution, review, copy or use of any of the information contained in or attached to this message is STRICTLY PROHIBITED. If you have received this transmission in error, please immediately notify us by reply e-mail, and destroy the original transmission and its attachments without reading them or saving them to disk. Thank you.
From | Date | Subject | |
---|---|---|---|
Next Message | David G. Johnston | 2020-03-11 13:45:52 | Re: How to set a value when NULL |
Previous Message | sivapostgres@yahoo.com | 2020-03-11 11:49:09 | Re: How to set a value when NULL |