Re: SQL Function Slowness, 8.3.0 - Mailing list pgsql-performance

From Gavin M. Roy
Subject Re: SQL Function Slowness, 8.3.0
Date
Msg-id af1bce590804161144q1b78be6cy69c9a44cc4b9b7bf@mail.gmail.com
Whole thread Raw
In response to Re: SQL Function Slowness, 8.3.0  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: SQL Function Slowness, 8.3.0
Re: SQL Function Slowness, 8.3.0
List pgsql-performance
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@sss.pgh.pa.us> wrote:
"Gavin M. Roy" <gmr@myyearbook.com> 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

pgsql-performance by date:

Previous
From: Bill Moran
Date:
Subject: Re: Background writer underemphasized ...
Next
From: "Joshua D. Drake"
Date:
Subject: Re: SQL Function Slowness, 8.3.0