| From: | Tobias Oberstein <tobias(dot)oberstein(at)gmail(dot)com> |
|---|---|
| To: | Federico Di Gregorio <fog(at)dndg(dot)it> |
| Cc: | psycopg(at)postgresql(dot)org |
| Subject: | Re: Session state per transaction |
| Date: | 2012-09-27 08:21:59 |
| Message-ID: | 50640CA7.9030803@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | psycopg |
Am 27.09.2012 09:47, schrieb Federico Di Gregorio:
> On 27/09/2012 09:35, Tobias Oberstein wrote:
>> My use case is this: all DB access is via Stored Procedures (SP) on a
>> pool of long lived DB connections. The set of eligible SPs is determined
>> in advance. Hence, something that does not lead to reparsing/replanning
>> of the SP call SELECT statements on every execution is desirable.
>>
>> I notice there is
>>
>> http://www.postgresql.org/docs/9.2/static/libpq-fastpath.html
>>
>> Does Psycopg support this?
>
> Nope.
;(
Then I am definitely interested in helping bringing support for prepared
stuff and also fastpath-SP-calls to Pscyopg (since the API for both seem
to be somewhat similar).
Tobias
>
> federico
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniele Varrazzo | 2012-09-28 01:32:42 | Prepared statements [was: Session state per transaction] |
| Previous Message | Federico Di Gregorio | 2012-09-27 07:47:58 | Re: Session state per transaction |