Re: Query slow as Function - Mailing list pgsql-performance

From Tom Lane
Subject Re: Query slow as Function
Date
Msg-id 27854.1329583042@sss.pgh.pa.us
Whole thread Raw
In response to Re: Query slow as Function  (Andreas Kretschmer <akretschmer@spamfence.net>)
Responses Re: Query slow as Function
Re: Query slow as Function
Re: Query slow as Function
List pgsql-performance
Andreas Kretschmer <akretschmer@spamfence.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.

            regards, tom lane

pgsql-performance by date:

Previous
From: Andreas Kretschmer
Date:
Subject: Re: Query slow as Function
Next
From: Andrew Dunstan
Date:
Subject: Re: Query slow as Function