<blockquote type="CITE"><pre>
<font color="#000000">Josh Berkus <<a href="mailto:josh@agliodbs.com">josh@agliodbs.com</a>> writes:</font>
<font color="#000000">> In recent versions, we've changed the logging of function executions so </font>
<font color="#000000">> that only the function call is logged, and not any of the queries which it </font>
<font color="#000000">> may execute internally. While most of the time this method is superior </font>
<font color="#000000">> for performance analysis, in applications with extensive multi-line stored </font>
<font color="#000000">> procedures sometimes you want to log each individual query.</font>
<font color="#000000">ISTM that the wave of the future for this is an instrumentation plug-in,</font>
<font color="#000000">not further kluging of the query logging functionality. I had the</font>
<font color="#000000">impression that Korry and EDB had some prototype capability in that</font>
<font color="#000000">direction already, and surely it shouldn't be that hard to write if not.</font>
</pre></blockquote><br /> There's a sort of "proof-of-concept" PL/pgSQL tracer plugin in the debugger project on
pgFoundry- I haven't played with it in a few months so I can't promise that it will run at the moment.<br /><br /> If
anyoneis interested, let me know and I'll add this to my ToDo list. <br /><br /> -- Korry