Re: Does a call to a language handler provide a context/session, and somewhere to keep session data? - Mailing list pgsql-general

From David G. Johnston
Subject Re: Does a call to a language handler provide a context/session, and somewhere to keep session data?
Date
Msg-id CAKFQuwYnorKZZOQH52DwQncceXAQvLCSp1QAgNu0YOcmYqVcNg@mail.gmail.com
Whole thread Raw
In response to Does a call to a language handler provide a context/session, and somewhere to keep session data?  (<david@andl.org>)
Responses Re: Does a call to a language handler provide a context/session, and somewhere to keep session data?  (<david@andl.org>)
Re: Does a call to a language handler provide a context/session, and somewhere to keep session data?  ("David Bennett" <davidb@pfxcorp.com>)
List pgsql-general
On Sun, Mar 6, 2016 at 10:21 PM, <david@andl.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?


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

David J.

pgsql-general by date:

Previous
From:
Date:
Subject: Does a call to a language handler provide a context/session, and somewhere to keep session data?
Next
From:
Date:
Subject: Re: "missing chunk number XX for toast value YY in pg_toast ..." after pg_basebackup.