From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Andreas Kretschmer <akretschmer(at)spamfence(dot)net>, Steve Horn <steve(at)stevehorn(dot)cc>, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Query slow as Function |
Date: | 2012-02-18 16:41:18 |
Message-ID: | 4F3FD4AE.30908@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On 02/18/2012 11:37 AM, Tom Lane wrote:
> Andreas Kretschmer<akretschmer(at)spamfence(dot)net> writes:
>> 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)
> Steve *is* using EXECUTE, so that doesn't seem to be the answer. I'm
> wondering about datatype mismatches myself --- the function form is
> forcing the parameter to be char(9), which is not a constraint imposed
> in the written-out query. There are lots of other possibilities
> though. It would be hard to say much without a self-contained example
> to try.
>
>
He's using EXECUTE ... USING. Does that plan with the used parameter?
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Steve Horn | 2012-02-18 17:15:05 | Re: Query slow as Function |
Previous Message | Tom Lane | 2012-02-18 16:37:22 | Re: Query slow as Function |