Comments on: Profiling stored procedures/functions

By: Matthew

Matthew — Sun, 18 Apr 2010 20:58:18 +0000

Yay! “AS 400″ selected here.

By: depesz

depesz — Sun, 18 Apr 2010 08:14:31 +0000

@Matthew:
heh, perhaps I should add a poll – “Do you like new layout”

But since, you made it to 3 – theme chooser is back

By: Matthew

Matthew — Sun, 18 Apr 2010 06:03:10 +0000

@depesz make that 3. At least people could choose the layout before.

By: depesz

depesz — Thu, 01 Apr 2010 10:31:49 +0000

@TOM:
no way. 2 people complained about new layout (you and metys), and all other opinions i got were: “YAY, it’s so much better than previous”.

By: Tom

Tom — Thu, 01 Apr 2010 10:27:32 +0000

Depesz WTF, this blog layout is awful. Bring back the old one.

By: depesz

depesz — Fri, 19 Mar 2010 23:07:39 +0000

@ASH:
sure. not sure though how’s that relevant. track_functions tracks how many times function was called. This blogpost is about checking how much time parts of function take.

By: ash

ash — Fri, 19 Mar 2010 23:01:33 +0000

ever tried track_functions in postgresql 8.4?

By: Brett

Brett — Thu, 18 Mar 2010 21:14:15 +0000

The edb-debugger module on pgfoundry also contains an excellent plpgsql profiling tool, which allows you to gather similar data (plus some). It’s less invasive (no code changes required) but you need to explicitly turn it on/off in each session to be traced.
I’m using it a bit to discover potential improvements in my plpgsql. By day I’m an Oracle developer, but I’ve found the postgres offering to be easier to use and more useful than Oracle’s dbms_profiler.

By: Johan

Johan — Thu, 18 Mar 2010 16:09:51 +0000

Thank you for this (and all your articles)! It allowed me to check and optimize a slow function (and revealed some really stupid thinking on my part) from 12 seconds to less than one!