Re: Postgres8.2 - turning off BINGLOG/PARSELOG

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Mario Splivalo <mario(dot)splivalo(at)mobart(dot)hr>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: Postgres8.2 - turning off BINGLOG/PARSELOG
Date: 2007-06-19 14:52:11
Message-ID: 20070619145211.GM4265@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Mario Splivalo wrote:
> 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 :)

> 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
>
> log_line_prefix = '%m [%p] <%d> %i'

One thing you should be aware of is that PARSELOG etc are really "PARSE"
and "LOG", but there is no intervening space since you put no space at
the end of log_line_prefix. So I suggest changing it to

log_line_prefix = '%m [%p] <%d> %i '

Now, regarding your question,

> 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)?

I don't think so. You can increase log_min_duration_statement a bit so
that only statements that take "long" are logged.

--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Joshua_Kramer 2007-06-19 14:54:06 Re: [pgsql-advocacy] [PERFORM] Postgres VS Oracle
Previous Message Robert Treat 2007-06-19 14:41:29 Re: [GENERAL] [PERFORM] [ADMIN] Postgres VS Oracle