pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bill Moran <wmoran@collaborativefusion.com>
To: Jim C. Nasby <jim@nasby.net>
Cc: Matthew Schumacher <matt.s@aptalaska.net>
Cc: pgsql-performance@postgresql.org
Subject: Re: Problems with inconsistant query performance.
Date: Thu, 28 Sep 2006 13:40:24 -0400
Message-ID: <20060928134024.bf09db28.wmoran@collaborativefusion.com> (raw)
In-Reply-To: <20060928161549.GN34238@nasby.net>
References: <451AC4E2.90106@aptalaska.net>
	<1c9501c6e2fb$91e30200$0c67a8c0@maniek>
	<451BE7CD.3060807@aptalaska.net>
	<20060928112843.0b6e3715.wmoran@collaborativefusion.com>
	<20060928161549.GN34238@nasby.net>

In response to "Jim C. Nasby" <jim@nasby.net>:

> On Thu, Sep 28, 2006 at 11:28:43AM -0400, Bill Moran wrote:
> > In response to Matthew Schumacher <matt.s@aptalaska.net>:
> > > 
> > > What I really need is a way to profile my proc when it runs slow so that
> > > I can resolve which of the queries is really slow.  Anyone with an idea
> > > on how to do this?
> > 
> > You could turn on statement logging and duration logging.  This would
> > give you a record of when things run and how long they take.  A little
> > work analyzing should show you which queries are running when your
> > favorite query slows down.
> 
> By default, that doesn't help you debug what's happening inside a
> function, because you only get the call to the function. I don't know if
> you can increase verbosity to combat that.

Right, but my point was that he believes another query is interfering
when the target query is slow.  Turning on those logging statements
will:
a) Allow him to identify times when the query is slow.
b) Identify other queries that are running at the same time.

If he sees a pattern (i.e. My query is always slow if query X5 is
running at the same time) he'll have a good lead into further research.

-- 
Bill Moran
Collaborative Fusion Inc.



view thread (11+ messages)

Message-ID: <20060928134024.bf09db28.wmoran@collaborativefusion.com>
Permalink:  ../20060928134024.bf09db28.wmoran@collaborativefusion.com/
Also on:    postgresql.org/message-id/20060928134024.bf09db28.wmoran@collaborativefusion.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 using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: wmoran@collaborativefusion.com, jim@nasby.net, matt.s@aptalaska.net
  Subject: Re: Problems with inconsistant query performance.
  In-Reply-To: <20060928134024.bf09db28.wmoran@collaborativefusion.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