Re: Wanted: way to limit logging

From: Herbert Rabago Ambos <herbert(at)hindang(dot)msuiit(dot)edu(dot)ph>
To: Jeff Boes <jboes(at)nexcerpt(dot)com>
Cc: <pgsql-admin(at)postgresql(dot)org>
Subject: Re: Wanted: way to limit logging
Date: 2001-10-11 17:51:17
Message-ID: Pine.LNX.4.30.0110111344060.9045-100000@hindang.msuiit.edu.ph
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin


start postgres with

-d 0

option, this time it would only display limited info such as DEBUG,
NOTICEs, ERROR: ON LINE NUM's... or check postgresql.conf file for more
option. In my configuration, i use

silent_mode = false

log_connections = true
log_timestamp = true
log_pid = true

debug_level = 0 #equivalent to -d 0

to monitor the logs.

Herbert

/**
* Database Administrator/Faculty
* MSU-Iligan Institute of Technology
* Philippines
*/

On Wed, 10 Oct 2001, Jeff Boes wrote:

> We've enabled logging from our database during development, using the
> option -l on the pg_ctl command. However, we get a lot of useless data:
>
> NOTICE: InvalidateSharedInvalid: cache state reset
>
> shows up a lot, and whenever an INSERT statement is executed, we get the
> statement as well as all the values. Is there a way to reduce the
> information spewed to the log? Ideally, we'd like to see only ERROR and
> DEBUG messages, not NOTICE; for statements, we'd like to see the SQL
> code, but have no interest in the values actually applied (some of our
> INSERT statements receive 10K of data).
>
>
>

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Stephan Szabo 2001-10-11 18:07:37 Re: Alter column / array
Previous Message Chad R. Larson 2001-10-11 17:15:43 Re: Database access error after upgrade 7.1.2 -> 7.1.3