Steve Horn <steve(at)stevehorn(dot)cc> wrote:
> Execute the function: select * from geocode_carrier_route_by_geocode('xyz');
> This query takes 500 milliseconds to run. My question of course is why?
The planner doesn't know the actual value of the input-parameter, so the
planner doesn't use the Index.
> Related: If I create a function and assign LANGUAGE 'sql', my function runs in
> the expected 10 milliseconds. Is there some overhead to using the plpgsql
The planner, in this case, knows the actual value.
> Thanks for any help in clarifying my understanding!
You can check the plan with the auto_explain - Extension, and you can
force the planner to create a plan based on the actual input-value by
using dynamic SQL (EXECUTE 'your query string' inside the function)
As i said, wild guess ...
Really, I'm not out to destroy Microsoft. That will just be a completely
unintentional side effect. (Linus Torvalds)
"If I was god, I would recompile penguin with --enable-fly." (unknown)
Kaufbach, Saxony, Germany, Europe. N 51.05082°, E 13.56889°
In response to
pgsql-performance by date
|Next:||From: Tom Lane||Date: 2012-02-18 16:37:22|
|Subject: Re: Query slow as Function |
|Previous:||From: Steve Horn||Date: 2012-02-18 15:03:46|
|Subject: Query slow as Function|