On Thu, Sep 28, 2006 at 11:28:43AM -0400, Bill Moran wrote: > In response to Matthew Schumacher <[EMAIL PROTECTED]>: > > > > 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. Something else to consider is that gettimeofday() on some platforms is painfully slow, which could completely skew all your numbers. -- Jim Nasby [EMAIL PROTECTED] EnterpriseDB http://enterprisedb.com 512.569.9461 (cell) ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
