| From: | Dave Cramer <pg(at)fastcrypt(dot)com> |
|---|---|
| To: | AMatveev(at)bitec(dot)ru |
| Cc: | Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com>, Craig Ringer <craig(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: One process per session lack of sharing |
| Date: | 2016-07-18 12:09:55 |
| Message-ID: | CADK3HHLPQ=b_vZvuJYtoJRHjCozLtwNf=givwxTPG-k0fLcTwQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 18 July 2016 at 06:04, <AMatveev(at)bitec(dot)ru> wrote:
> Hi
>
> > There's https://github.com/jnr/jnr-ffi that enables to call C
> > functions without resorting to writing JNI wrappers.
> I have not said that you are wrong.
> It's the dark side of "like seprate process"
> They can cheaply call sql from jvm.
> And they can't cheaply call jvm from sql.
>
This https://github.com/davecramer/plj-new is a very old project that did
work at one time which attempted to do RPC calls to the jvm to address
exactly this problem.
However "cheaply" calling jvm from sql or vice-versa is not really possible.
I do like the idea of the background worker and shared memory though.
Dave Cramer
davec(at)postgresintl(dot)com
www.postgresintl.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Merlin Moncure | 2016-07-18 13:37:01 | Re: DO with a large amount of statements get stuck with high memory consumption |
| Previous Message | Magnus Hagander | 2016-07-18 11:10:36 | Re: pg_xlogdump follow into the future |