Re: Does a call to a language handler provide a context/session, and somewhere to keep session data?

Thank you for your response.

Yes, I was aware of GD and SD. My question is about what facilities Postgres provides for implementing such a thing. Where is the proper place for the root of the SD/GD? What does an implementation use to determine that two calls belong to the same session?

I’m not finding that easy to understand by reading source code.

Regards

David M Bennett FACS

_____

MD Powerflex Corporation, creators of PFXplus

To contact us, please call +61-3-9548-9114 or go to <http://www.pfxcorp.com/contact.htm> www.pfxcorp.com/contact.htm

From: pgsql-general-owner(at)postgresql(dot)org [mailto:pgsql-general-owner(at)postgresql(dot)org] On Behalf Of David G. Johnston
Sent: Monday, 7 March 2016 4:28 PM
To: david(at)andl(dot)org
Cc: pgsql-general-owner+M220479=david=andl(dot)org(at)postgresql(dot)org; pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: [GENERAL] Does a call to a language handler provide a context/session, and somewhere to keep session data?

On Sun, Mar 6, 2016 at 10:21 PM, <david(at)andl(dot)org <mailto:david(at)andl(dot)org> > wrote:

Given that a language handler would be expected to be persistent, and to support concurrent (and reentrant) calls within a single database, is there a unique context or session identifier available?

Is there a place to store data, to be retrieved later in the same session?

Is there a place to store data (a cache?) that has been retrieved from the database for use by concurrent sessions using that database?

http://www.postgresql.org/docs/9.5/interactive/plpython-sharing.html

​PL/R also has an implementation for this kind of thing.

David J.