pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Scott Marlowe <smarlowe@g2switchworks.com>
To: Pallav Kalva <pkalva@deg.cc>
Cc: pgsql-admin@postgresql.org
Subject: Re: SQL logging (log_min_duration_statement) not working
Date: Wed, 18 May 2005 09:39:30 -0500
Message-ID: <1116427170.31821.10.camel@state.g2switchworks.com> (raw)
In-Reply-To: <428B4487.8010702@deg.cc>
References: <428B4487.8010702@deg.cc>

On Wed, 2005-05-18 at 08:35, Pallav Kalva wrote:
> Hi Everybody,
> 
> 
>     I am having problems with logging long running SQL in the log file. 
> I have set log_min_duration_statement = 5000 (5secs) and it is not 
> logging sql statements that took over 5 secs and this is only from 
> queries generated by Hibernate . here is a sample query from hibernate :
> 
> -----------------------------------------------------------------------------------------
> select listingadd1_.addressid as col_0_0_
> from listing.listing listing0_, listing.address listingadd1_
> where ((select count(taxrolls2_.fkaddressid)
>        from listing.taxroll taxrolls2_
>        where listingadd1_.addressid=taxrolls2_.fkaddressid)=0 )
>        and(listing0_.fkbestaddressid=listingadd1_.addressid )
>        and(listing0_.entrydate>$1 )
> order by  listingadd1_.addressid asc
> --------------------------------------------------------------------------------------------
> 
>   This above query take more than 5 secs to run and it wont get logged , 
> where as all other queries which are not generated by Hibernate are 
> logged. Is this expected behavior ?  am I missing something else ?  
> Please advice.

Are you sure it's taking more than 5 seconds to run, not that it's
taking <5 seconds to run and >5 seconds to return the data.  I'm pretty
sure the time it takes to ship out the data isn't counted in the time
used to decide whether to log the query or not by the postmaster.

I.e. what does explain analyze QUERY HERE say about the execution time?



view thread (10+ messages)  latest in thread

Message-ID: <1116427170.31821.10.camel@state.g2switchworks.com>
Permalink:  ../1116427170.31821.10.camel@state.g2switchworks.com/
Also on:    postgresql.org/message-id/1116427170.31821.10.camel@state.g2switchworks.com

 · 

reply

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: smarlowe@g2switchworks.com, pkalva@deg.cc
  Subject: Re: SQL logging (log_min_duration_statement) not working
  In-Reply-To: <1116427170.31821.10.camel@state.g2switchworks.com>
  References: <428B4487.8010702@deg.cc> <1116427170.31821.10.camel@state.g2switchworks.com>

* 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