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

Re: postgres seems to ignore log_min_duration_statement

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Martin A(dot) Brooks" <martin(at)antibodymx(dot)net>, Vladimir Rusinov <vladimir(at)greenmice(dot)info>, pgsql-admin(at)postgresql(dot)org
Subject: Re: postgres seems to ignore log_min_duration_statement
Date: 2008-10-16 02:17:58
Message-ID: 200810160217.m9G2HwL03422@momjian.us (view raw or flat)
Thread:
Lists: pgsql-admin
Tom Lane wrote:
> "Martin A. Brooks" <martin(at)antibodymx(dot)net> writes:
> > I don't explicitly set that parameter in my config.  The full config 
> > file can be found at  http://www.antibodymx.net/postgresql.conf
> 
> You've got log_duration on; that overrides log_min_duration_statement
> and forces statement durations to always be logged.
> 
> (No, I'm not quite sure why we have both variables ...)

I believe log_duration prints just the duration and assumes you printed
the statement previously (when it arrived).  log_min_duration_statement
by definition has to print after the statement completes.

-- 
  Bruce Momjian  <bruce(at)momjian(dot)us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +

In response to

pgsql-admin by date

Next:From: Martin BadieDate: 2008-10-16 08:10:27
Subject: Re: replication with table add/removes..
Previous:From: Fabrízio de Royes MelloDate: 2008-10-15 21:48:18
Subject: Re: backup server - how to disconnect

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