Heeeey the raise notice is a good idea, thanks. I use raise notice already for other uses, may as well go with it. Thanks.
Matthew Hartman Programmer/Analyst Information Management, ICP Kingston General Hospital (613) 549-6666 x4294 -----Original Message----- From: Merlin Moncure [mailto:mmonc...@gmail.com] Sent: Tuesday, June 23, 2009 9:20 AM To: Hartman, Matthew Cc: pgsql-general@postgresql.org Subject: Re: [GENERAL] Explaining functions. On Tue, Jun 23, 2009 at 8:03 AM, Hartman, Matthew<matthew.hart...@krcc.on.ca> wrote: > Is there a recommended approach when trying to use EXPLAIN on a > function? Specifically, a function that is more than the typical SELECT > statement or tiny loop. The one in question that I'm hoping to optimize > is around 250 lines. What I normally do for benchmarking of complex functions is to sprinkle the source with "raise notice '%', timeofday();" to figure out where the bottlenecks are. Following that, I micro-optimize problem queries or expressions outside of the function body in psql. merlin -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
