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
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
---(end of broadcast)---
TIP 4: Have you searched our list archives?
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
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
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
