Re: TODO list: Allow Java server-side programming - Mailing list pgsql-hackers

From Hannu Krosing
Subject Re: TODO list: Allow Java server-side programming
Date
Msg-id 3A7D1E51.E383AB7F@tm.ee
Whole thread Raw
In response to TODO list: Allow Java server-side programming  (tomasz konefal <twkonefal@yahoo.ca>)
Responses Re: TODO list: Allow Java server-side programming  (Peter Mount <peter@retep.org.uk>)
List pgsql-hackers
Peter Mount wrote:
> 
> At 14:57 02/02/01 -0500, Alex Pilosov wrote:
> >On Fri, 2 Feb 2001, tomasz konefal wrote:
> >
> > >   could someone please clarify what "Allow Java
> > > server-side programming" actually means?  what are the
> > > limitations of using java and jdbc with pgsql?
> >
> >It means to embed Java interpreter inside postgres, and allow writing
> >stored procedures and triggers in Java.
> 
> Thats correct. Basically you are talking of something like PL/Java. The
> Java side would be simple, but its linking the JVM to the backend that's
> the problem.
> 
> It's been a while since I delved into the backend, but unless it's changed
> from fork() to threading,

Someone posted here recently his port/tweaks of backend so that it used 
threads instead of fork(). IIRC it was done to be used inside a java 
client in an embedded system.

----------------
Hannu


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Reminder about Announce/General lists
Next
From: Hannu Krosing
Date:
Subject: Re: Like vs '=' bug with indexing