From: | Jan de Visser <jan(at)de-visser(dot)net> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Cc: | david(at)andl(dot)org, pgsql-general-owner+M220529=david=andl(dot)org(at)postgresql(dot)org |
Subject: | Re: Does a call to a language handler provide a context/session, and somewhere to keep session data? |
Date: | 2016-03-08 00:46:19 |
Message-ID: | 2773154.9cXRjvk1m4@coyote |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On March 8, 2016 11:35:00 AM david(at)andl(dot)org wrote:
> From: pgsql-general-owner(at)postgresql(dot)org
> [mailto:pgsql-general-owner(at)postgresql(dot)org] On Behalf Of John R Pierce
>
> this stuff you're loading from the database once, that's just data about
> your language plugin's configuration, or is it user data, or what? [dmb>]
> It's the catalog for Andl. It contains defined functions, types, persistent
> scalar (non table) data values and links to tables.
>
> if its just a few global settings, you should consider using custom
> settings variables, rather than database tables. for instance, pljava has
> a setting, pljava.libjvm_location='/usr/lib/jvm/java-1.8.0/lib/libjvm.so'
> or whatever which it uses to find the Java native calls interface
> library... [dmb>] Andl has something similar, but that problem is already
> solved.
You're being pretty oblique about what it is you're trying to achieve.
To go back to one of your earlier emails: the hardest problem in computing
isn't cache invalidation. It is clearly explaining what the problem at hand
is.
From | Date | Subject | |
---|---|---|---|
Next Message | Craig Ringer | 2016-03-08 02:05:04 | Re: Slave-Master replication on top of BDR |
Previous Message | david | 2016-03-08 00:35:00 | Re: Does a call to a language handler provide a context/session, and somewhere to keep session data? |