Re: Pl/Python runtime overhead
От | Seref Arikan |
---|---|
Тема | Re: Pl/Python runtime overhead |
Дата | |
Msg-id | CA+4ThdpfCjyy+ySidwFW0_CJp5=wF9Bzjf8h+4bAKnrjzDuj7A@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Pl/Python runtime overhead (Peter Eisentraut <peter_e@gmx.net>) |
Список | pgsql-general |
Thanks for the confirmation Peter,
I guess I'll take a good look at the existing implementations.
All the best
Seref
On Fri, Aug 9, 2013 at 10:24 PM, Peter Eisentraut <peter_e@gmx.net> wrote:
On 8/7/13 10:43 AM, Seref Arikan wrote:The Python interpreter is initialized once during a session, normally
> 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?
when the first PL/Python function is called. So yes, connection pooling
can be helpful here.The basic documentation is 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.
http://www.postgresql.org/docs/devel/static/plhandler.html. The rest is
mainly experience and copying from existing language handler
implementations.
В списке pgsql-general по дате отправления: