| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl> |
| Cc: | Mike Nolan <nolan(at)gw(dot)tssi(dot)com>, pgsql general list <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Tuning queries inside a function |
| Date: | 2005-04-29 19:50:47 |
| Message-ID: | 42729017.9060805@commandprompt.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
>
> Huh, sorry, this doesn't work ... we don't allow DECLARE for EXPLAIN.
> It'd be neat though ...
What about having a debug mode for the function. E.g:
selet * from foo('bar','debug')
When you run with debug it actually runs the function but outputs
notices that are the explain anaylze of each function? You might
I would have to check be able to include a timestamp at the beginning
of each notice.
This will allow you to figure out where your slow downs are that are
not query related?
Sincerely,
Joshua D. Drake
>
--
Your PostgreSQL solutions company - Command Prompt, Inc. 1.800.492.2240
PostgreSQL Replication, Consulting, Custom Programming, 24x7 support
Managed Services, Shared and Dedication Hosting
Co-Authors: plPHP, plPerlNG - http://www.commandprompt.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | typing80wpm | 2005-04-29 20:40:57 | p2p ip connection problems |
| Previous Message | Alvaro Herrera | 2005-04-29 19:36:01 | Re: Tuning queries inside a function |