From: Alvaro Herrera <alvherre@commandprompt.com>
To: Mario Splivalo <mario.splivalo@mobart.hr>
Cc: pgsql-admin@postgresql.org
Subject: Re: Postgres8.2 - turning off BINGLOG/PARSELOG
Date: Tue, 19 Jun 2007 10:52:11 -0400
Message-ID: <20070619145211.GM4265@alvh.no-ip.org> (raw)
In-Reply-To: <1182263472.13561.43.camel@localhost.localdomain>
References: <1182263472.13561.43.camel@localhost.localdomain>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: alvherre@commandprompt.com, mario.splivalo@mobart.hr
Subject: Re: Postgres8.2 - turning off BINGLOG/PARSELOG
In-Reply-To: <20070619145211.GM4265@alvh.no-ip.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
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