Skip site navigation (1) Skip section navigation (2)

Postgres8.2 - turning off BINGLOG/PARSELOG

From: Mario Splivalo <mario(dot)splivalo(at)mobart(dot)hr>
To: pgsql-admin(at)postgresql(dot)org
Subject: Postgres8.2 - turning off BINGLOG/PARSELOG
Date: 2007-06-19 14:31:12
Message-ID: 1182263472.13561.43.camel@localhost.localdomain (view raw or flat)
Thread:
Lists: pgsql-admin
I'm finaly switching to 8.2. I notice that ugly 'feature' from pg8.1 has
been fixed: logging the parametars of prepared statements. It's a bit
ugly, but it's there :)

But now in my log i have BINDLOG, PARSELOG and others, and my log looks
realy cloged. Here is an example. I'm calling the
'create_mo_sms_message' function via JDBC, and this is the log entry:

2007-06-19 16:22:15.553 CEST [4596] <octopussy2> BINDLOG:  duration:
0.023 ms  bind S_1: BEGIN
2007-06-19 16:22:15.553 CEST [4596] <octopussy2> BEGINLOG:  duration:
0.010 ms  execute S_1: BEGIN
2007-06-19 16:22:15.553 CEST [4596] <octopussy2> PARSELOG:  duration:
0.165 ms  parse <unnamed>: select * from create_mo_sms_message($1, $2,
$3, $4, $5, $6, $7, $8, $9, $10, $11) as result
2007-06-19 16:22:15.553 CEST [4596] <octopussy2> BINDLOG:  duration:
0.292 ms  bind <unnamed>: select * from create_mo_sms_message($1, $2,
$3, $4, $5, $6, $7, $8, $9, $10, $11) as result
2007-06-19 16:22:15.553 CEST [4596] <octopussy2> BINDDETAIL:
parameters: $1 = NULL, $2 = 'a9369fa8-2bd9-41f0-a325-cd0fe62fbe46', $3 =
'+38598111111', $4 = 'PULITZER-1', $5 = 'memo Ovo je moja mala
probetina...', $6 = '2007-06-19 14:22:15.547', $7 = NULL, $8 = NULL, $9
= '127.0.0.1', $10 = 'tele2', $11 = NULL
2007-06-19 16:22:15.554 CEST [4596] <octopussy2> SELECTNOTICE:
__internal__determine_operator_id: Operator_mark >tele2< does not
exists!
2007-06-19 16:22:15.554 CEST [4596] <octopussy2> SELECTCONTEXT:
PL/pgSQL function "create_mo_sms_message" line 24 at assignment
2007-06-19 16:22:15.554 CEST [4596] <octopussy2> SELECTNOTICE:
CREATE_MO: Operator_id could not be guessed...
2007-06-19 16:22:15.554 CEST [4596] <octopussy2> SELECTLOG:  duration:
0.599 ms  execute <unnamed>: select * from create_mo_sms_message($1, $2,
$3, $4, $5, $6, $7, $8, $9, $10, $11) as result
2007-06-19 16:22:15.554 CEST [4596] <octopussy2> SELECTDETAIL:
parameters: $1 = NULL, $2 = 'a9369fa8-2bd9-41f0-a325-cd0fe62fbe46', $3 =
'+38598111111', $4 = 'PULITZER-1', $5 = 'memo Ovo je moja mala
probetina...', $6 = '2007-06-19 14:22:15.547', $7 = NULL, $8 = NULL, $9
= '127.0.0.1', $10 = 'tele2', $11 = NULL
2007-06-19 16:22:15.555 CEST [4596] <octopussy2> BINDLOG:  duration:
0.027 ms  bind S_2: COMMIT
2007-06-19 16:22:15.556 CEST [4596] <octopussy2> COMMITLOG:  duration:
0.029 ms  execute S_2: COMMIT


These are the settings from postgresql.conf, concerning loging:

log_min_messages = info
log_min_duration_stateme
log_error_verbosity = defaultnt = 0
debug_print_parse = off
debug_print_rewritten = off
debug_pretty_print = off
log_line_prefix = '%m [%p] <%d> %i'

Is there a way to turn off these PARSELOG and BINDLOG messages? I realy
need only the SELECTLOG (and SELECTDETAIL because there are the actuall
parametars)?

Tia,

	Mario


Responses

pgsql-admin by date

Next:From: Robert TreatDate: 2007-06-19 14:41:29
Subject: Re: [GENERAL] [PERFORM] [ADMIN] Postgres VS Oracle
Previous:From: Kevin GrittnerDate: 2007-06-19 14:10:47
Subject: Re: Explained by known hardware failures, or keeplooking?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group