From: | Grzegorz Jaśkiewicz <gryzman(at)gmail(dot)com> |
---|---|
To: | "Julius Tuskenis" <julius(dot)tuskenis(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: SQL plan in functions |
Date: | 2008-12-18 09:21:18 |
Message-ID: | 2f4958ff0812180121x4bf637em39db2a3ba63a9044@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, Dec 18, 2008 at 9:18 AM, Julius Tuskenis
<julius(dot)tuskenis(at)gmail(dot)com> wrote:
> 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?
use EXECUTE 'query' .
--
GJ
From | Date | Subject | |
---|---|---|---|
Next Message | A. Kretschmer | 2008-12-18 09:28:44 | Re: SQL plan in functions |
Previous Message | Jonatan Evald Buus | 2008-12-18 09:18:13 | Re: Prevent new timeline during archive recovery |