pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedLogging questions
2+ messages / 2 participants
[nested] [flat]
* Logging questions
@ 2010-12-10 18:01 Wells Oliver <woliver@padres.com>
0 siblings, 1 reply; 2+ messages in thread
From: Wells Oliver @ 2010-12-10 18:01 UTC (permalink / raw)
To: pgsql-admin
Hello- a quick question about logging. I'm trying to set logging to the
most minimal level possible. e.g. I really don't want to see the
following kind of thing:
2010-12-10 09:59:40 PST FATAL: database "woliver" does not exist
Because... so what? Some guy forgot to supply the DB name. I've looked
over the logging options in the documentation and they are legion. What
are my key options to reduce logging to the lowest, most vital sort of
messages?
Thanks for tips!
--
Wells Oliver
Developer, Baseball Systems
San Diego Padres | 100 Park Boulevard | San Diego CA 92101
^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: Logging questions
@ 2010-12-10 22:49 Peter Eisentraut <peter_e@gmx.net>
parent: Wells Oliver <woliver@padres.com>
0 siblings, 0 replies; 2+ messages in thread
From: Peter Eisentraut @ 2010-12-10 22:49 UTC (permalink / raw)
To: Wells Oliver <woliver@padres.com>; +Cc: pgsql-admin
On fre, 2010-12-10 at 10:01 -0800, Wells Oliver wrote:
> Hello- a quick question about logging. I'm trying to set logging to the
> most minimal level possible. e.g. I really don't want to see the
> following kind of thing:
>
> 2010-12-10 09:59:40 PST FATAL: database "woliver" does not exist
>
> Because... so what? Some guy forgot to supply the DB name. I've looked
> over the logging options in the documentation and they are legion. What
> are my key options to reduce logging to the lowest, most vital sort of
> messages?
The problem is, the distinction of severity is actually not so much
about what is important to you the DBA, but what is important to the
session process. The above is important to the session process because
the session cannot continue after that error. Other, more severe
problems will only show up as "error" because the session can continue.
So unless you want to set log_min_messages to panic, which pretty much
means that by the time you see the message your database system is dead,
you probably want to log everything at least on level error or warning
and then rely on a log analysis tool and/or other monitoring to work out
what is important to you.
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2010-12-10 22:49 UTC | newest]
Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2010-12-10 18:01 Logging questions Wells Oliver <woliver@padres.com>
2010-12-10 22:49 ` Peter Eisentraut <peter_e@gmx.net>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox