| From: | "A(dot) Kretschmer" <andreas(dot)kretschmer(at)schollglas(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: SQL plan in functions |
| Date: | 2008-12-18 09:28:44 |
| Message-ID: | 20081218092844.GA8458@a-kretschmer.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
In response to Julius Tuskenis :
> Hello, list.
>
> I have a function witch returns record set. What troubles me is that
> depending on parameters I pass to this function the execution time
> varies greatly. On the other hand if I execute the query (not the
> function) with pgAdmin - it gives results quickly.
> In previous post You helped me realize, that the problem was because the
> function has only one plan of SQL inside no matter the parameters
> values. Is there a way to order postgres to check the plan each time the
> function is called?
Sure, use EXECUTE 'your sql' inside the function to force the planner to
generate a new plan depending on the current parameters.
Regards, Andreas
--
Andreas Kretschmer
Kontakt: Heynitz: 035242/47150, D1: 0160/7141639 (mehr: -> Header)
GnuPG-ID: 0x3FFF606C, privat 0x7F4584DA http://wwwkeys.de.pgp.net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Raymond O'Donnell | 2008-12-18 10:45:01 | Re: Error: Operator does not exist: "char"=integer |
| Previous Message | Grzegorz Jaśkiewicz | 2008-12-18 09:21:18 | Re: SQL plan in functions |