Re: One process per session lack of sharing - Mailing list pgsql-hackers

From AMatveev@bitec.ru
Subject Re: One process per session lack of sharing
Date
Msg-id 118456757.20160718164155@bitec.ru
Whole thread Raw
In response to Re: One process per session lack of sharing  (Dave Cramer <pg@fastcrypt.com>)
Responses Re: One process per session lack of sharing  (Greg Stark <stark@mit.edu>)
List pgsql-hackers
Hi

> 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.

It's not opposite concepts. It's like two level cache.
Something    is   best   with   shared memory.
When "a sharing of upper layer" is best with shared process.
And there is something that should not sharing at all.
Any deviation is always overhead.

But to be honest I  really do not like "sharing".
It is against human nature. 
And  I  will  be  really happy when there are processors with infinite
performance and memory with infinite size.
:)))








pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: DO with a large amount of statements get stuck with high memory consumption
Next
From: Jan Wieck
Date:
Subject: Re: DO with a large amount of statements get stuck with high memory consumption