| From: | Seref Arikan <serefarikan(at)kurumsalteknoloji(dot)com> |
|---|---|
| To: | PG-General Mailing List <pgsql-general(at)postgresql(dot)org> |
| Subject: | Pl/Python runtime overhead |
| Date: | 2013-08-07 14:43:13 |
| Message-ID: | CA+4Thdqnyh5at+VoEVtZ-jaLf1RO-pA=xHtv9x40Lw3c2gs7eA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Greetings,
Somehow I have failed to find the appropriate keywords for successful
results for my question.
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?
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.
Regards
Seref
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Igor Neyman | 2013-08-07 14:44:17 | Re: Self referencing composite datatype |
| Previous Message | David Johnston | 2013-08-07 14:34:37 | Re: Self referencing composite datatype |