Thread: profiling PL/pgSQL?
I have 700 lines of non-performant pgSQL code that I'd like to profile to see what's going on. What's the best way to profile stored procedures? Thanks, Drew
am Fri, dem 03.11.2006, um 3:12:14 -0800 mailte Drew Wilson folgendes: > I have 700 lines of non-performant pgSQL code that I'd like to > profile to see what's going on. > > What's the best way to profile stored procedures? RAISE NOTICE, you can raise the aktual time within a transaction with timeofday() Andreas -- Andreas Kretschmer Kontakt: Heynitz: 035242/47215, D1: 0160/7141639 (mehr: -> Header) GnuPG-ID: 0x3FFF606C, privat 0x7F4584DA http://wwwkeys.de.pgp.net
A. Kretschmer wrote: > am Fri, dem 03.11.2006, um 3:12:14 -0800 mailte Drew Wilson folgendes: >> I have 700 lines of non-performant pgSQL code that I'd like to >> profile to see what's going on. >> >> What's the best way to profile stored procedures? > > RAISE NOTICE, you can raise the aktual time within a transaction with > timeofday() Of course you only have very small values of "best" available with plpgsql debugging. There's a GUI debugger from EnterpriseDB I believe, but I've no idea how good it is. Any users/company bods care to let us know? -- Richard Huxton Archonet Ltd
On 11/3/06, Richard Huxton <dev@archonet.com> wrote: > There's a GUI debugger from EnterpriseDB I believe, but I've no idea how > good it is. Any users/company bods care to let us know? If you visit: http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/edb-debugger/#dirlist We have both a PL/pgSQL profiler and tracer available. -- Jonah H. Harris, Software Architect | phone: 732.331.1300 EnterpriseDB Corporation | fax: 732.331.1301 33 Wood Ave S, 2nd Floor | jharris@enterprisedb.com Iselin, New Jersey 08830 | http://www.enterprisedb.com/
> am Fri, dem 03.11.2006, um 3:12:14 -0800 mailte Drew Wilson folgendes: >> I have 700 lines of non-performant pgSQL code that I'd like to >> profile to see what's going on. >> >> What's the best way to profile stored procedures? > > RAISE NOTICE, you can raise the aktual time within a transaction with > timeofday() Of course you only have very small values of "best" available with plpgsql debugging. There's a GUI debugger from EnterpriseDB I believe, but I've no idea how good it is. Any users/company bods care to let us know?
It's an excellent debugger (of course, I'm a bit biased).
We are working on open-sourcing it now - we needed some of the plugin features in 8.2.
As Jonah pointed out, we also have a PL/pgSQL profiler (already open-sourced but a bit tricky to build). The profiler tells you how much CPU time you spent at each line of PL/pgSQL code, how many times you executed each line of code, and how much I/O was caused by each line (number of scans, blocks fetched, blocks hit, tuples returned, tuples fetched, tuples inserted, tuples updated, tuples deleted).
It's been a while since I looked at it, but I seem to remember that it spits out an XML report that you can coax into a nice HTML page via the XSLT.
The plugin_profiler needs to be converted over to the plugin architecture in 8.2, but that's not a lot of work.
-- Korry
-- Korry Douglas korryd@enterprisedb.com EnterpriseDB http://www.enterprisedb.com |