From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | Seref Arikan <serefarikan(at)kurumsalteknoloji(dot)com> |
Cc: | PG-General Mailing List <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Pl/Python runtime overhead |
Date: | 2013-08-09 21:24:09 |
Message-ID: | 52055DF9.2010006@gmx.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 8/7/13 10:43 AM, Seref Arikan wrote:
> When a pl/python based function is invoked, does it keep a python
> runtime running across calls to same function? That is, if I use
> connection pooling, can I save on the python runtime initialization and
> loading costs?
The Python interpreter is initialized once during a session, normally
when the first PL/Python function is called. So yes, connection pooling
can be helpful here.
> Are there any documents/books etc you'd recommend to get a good
> understanding of extending postgres with languages like python? I'd
> really like to get a good grip of the architecture of this type of
> extension, and possibly attempt to introduce a language of my own
> choosing. The docs I've seen so far are mostly too specific, making it a
> bit for hard for me to see the forest from the trees.
The basic documentation is here:
http://www.postgresql.org/docs/devel/static/plhandler.html. The rest is
mainly experience and copying from existing language handler
implementations.
From | Date | Subject | |
---|---|---|---|
Next Message | Kevin Grittner | 2013-08-09 21:28:21 | Re: bi-directional syncing help request |
Previous Message | Day, David | 2013-08-09 21:18:46 | Re: plpgsql FOR LOOP CTE problem ? |