Re: Pl/Python runtime overhead

From: Seref Arikan <serefarikan(at)kurumsalteknoloji(dot)com>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: PG-General Mailing List <pgsql-general(at)postgresql(dot)org>
Subject: Re: Pl/Python runtime overhead
Date: 2013-08-12 08:35:10
Message-ID: CA+4ThdpfCjyy+ySidwFW0_CJp5=wF9Bzjf8h+4bAKnrjzDuj7A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)gmx(dot)net> wrote:

> 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.
>
>

In response to

Browse pgsql-general by date

  From Date Subject
Next Message raghu ram 2013-08-12 09:31:53 Re: Trigger to update table info
Previous Message Arvind Singh 2013-08-12 07:16:33 Trigger to update table info