From: Tom Lane <tgl@sss.pgh.pa.us>
To: Mindaugas <mind@bi.lt>
Cc: pgsql-performance@postgresql.org
Subject: Re: How to analyze function performance
Date: Thu, 15 Jun 2006 10:24:04 -0400
Message-ID: <27705.1150381444@sss.pgh.pa.us> (raw)
In-Reply-To: <016401c69075$8a35e8c0$f20214ac@bite.lt>
References: <016401c69075$8a35e8c0$f20214ac@bite.lt>
"Mindaugas" <mind@bi.lt> writes:
> Is it possible to somehow analyze function performance? E.g.
> we are using function cleanup() which takes obviously too much time
> to execute but I have problems trying to figure what is slowing things
> down.
> When I explain analyze function lines step by step it show quite
> acceptable performance.
Are you sure you are "explain analyze"ing the same queries the function
is really doing? You have to account for the fact that what plpgsql is
issuing is parameterized queries, and sometimes that limits the
planner's ability to pick a good plan. For instance, if you have
declare x int;
begin
...
for r in select * from foo where key = x loop ...
then what is really getting planned and executed is "select * from foo
where key = $1" --- every plpgsql variable gets replaced by a parameter
symbol "$n". You can model this for EXPLAIN purposes with a prepared
statement:
prepare p1(int) as select * from foo where key = $1;
explain analyze execute p1(42);
If you find out that a particular query really sucks when parameterized,
you can work around this by using EXECUTE to force the query to be
planned afresh on each use with literal constants instead of parameters:
for r in execute 'select * from foo where key = ' || x loop ...
The replanning takes extra time, though, so don't do this except where
you've specifically proved there's a need.
BTW, be careful to use quote_literal() when needed in queries built as
strings, else you'll have bugs and maybe even security problems.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, mind@bi.lt
Subject: Re: How to analyze function performance
In-Reply-To: <27705.1150381444@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox