| From: | Dave Cramer <pg(at)fastcrypt(dot)com> |
|---|---|
| To: | John Lister <john(dot)lister(at)kickstone(dot)com> |
| Cc: | Thomas Finneid <tfinneid(at)fcon(dot)no>, pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: pooled prepared statements |
| Date: | 2009-05-13 15:21:42 |
| Message-ID: | 491f66a50905130821j6afa056fp947e4dbcfd09d701@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
On Wed, May 13, 2009 at 10:37 AM, John Lister <john(dot)lister(at)kickstone(dot)com>wrote:
> Probably easier to create a server side function instead, then.
>>>>
>>> But wouldn't you still have to go through all the planning steps within
>>> the function for any queries, although i'll admit i'm not familiar with
>>> Postgresql functions.
>>>
>>
>> Server-side functions are compiled when installed. Since my function would
>> only contain simple queries that are parameterized, it would pre-compile
>> well.
>>
>
While the function may be compiled, the overhead is the same for preparing
the statement inside the function. So I don't think it's a huge win.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Finneid | 2009-05-13 19:52:03 | Re: pooled prepared statements |
| Previous Message | Vernon | 2009-05-13 15:06:43 | [Fwd: Re: Enums - from java to jpa] |