Re: SQL Function Slowness, 8.3.0

------=_Part_20860_23503872.1208371480588
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

After detailed examination of pg_stat_user_indexes usage, it's clear that
the functions don't use the same indexes.  I've casted everything to match
the indexes in the SQL function, to no success.  Any suggestions on next
steps?  Maybe for 8.4 we could find a way to explain analyze function
internals ;-)
Gavin

On Wed, Apr 16, 2008 at 11:09 AM, Tom Lane <tgl@[EMAIL PROTECTED]
> wrote:

> "Gavin M. Roy" <gmr@[EMAIL PROTECTED]
> writes:
> > In 8.3.0, I'm seeing some oddities with SQL functions which I thought
> were
> > immune to the planner data restrictions of plpgsql functions and the
> sort.
>
> Without a specific example this discussion is pretty content-free, but
> in general SQL functions face the same hazards of bad parameterized
> plans as plpgsql functions do.
>
>                        regards, tom lane
>

------=_Part_20860_23503872.1208371480588
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

After detailed examination of pg_stat_user_indexes usage, it&#39;s clear
that the functions don&#39;t use the same indexes. &nbsp;I&#39;ve casted
everything to match the indexes in the SQL function, to no success.
&nbsp;Any suggestions on next steps? &nbsp;Maybe for 8.4 we could find a
way to explain analyze function internals ;-)<div>
<br></div><div>Gavin<br><br><div class="gmail_quote">On Wed, Apr 16, 2008
at 11:09 AM, Tom Lane &lt;<a
href="mailto:tgl@[EMAIL PROTECTED]
">tgl@[EMAIL PROTECTED]
>&gt;
wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="Ih2E3d">&quot;Gavin M. Roy&quot; &lt;<a
href="mailto:gmr@[EMAIL PROTECTED]
">gmr@[EMAIL PROTECTED]
>&gt; writes:<br>
&gt; In 8.3.0, I&#39;m seeing some oddities with SQL functions which I
thought were<br>
&gt; immune to the planner data restrictions of plpgsql functions and the
sort.<br>
<br>
</div>Without a specific example this discussion is pretty content-free,
but<br>
in general SQL functions face the same hazards of bad parameterized<br>
plans as plpgsql functions do.<br>
<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp;regards, tom lane<br>
</blockquote></div><br></div>

------=_Part_20860_23503872.1208371480588--