From: | Doug McNaught <doug(at)wireboard(dot)com> |
---|---|
To: | Nic Ferrier <nferrier(at)tapsellferrier(dot)co(dot)uk> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: implemention of calls to stored procs. |
Date: | 2002-01-23 02:01:38 |
Message-ID: | m3g04x6d19.fsf@varsoon.denali.to |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Nic Ferrier <nferrier(at)tapsellferrier(dot)co(dot)uk> writes:
> It's not terribly difficult to crack this actually... I was going to
> use GCJ as a platform for a base java class that could be used like a
> quick C stored proc.
Interesting approach. The other person that posted recently was going
to run Java as a separate daemon, since the idea of linking postgres
with the JVM was causing loud gagging sounds among the members of this
list (for reasons I agree with).
Are you talking about Java compiled to native code rather than
bytecode? I know GCJ can do that and it would seem to be a better way
to do this (since you can already link in native compiled C
libraries).
The other thing to be aware of is that, if GCJ requires linking with
thread libraries, you may have some problems, since the PG backend
itself is not threaded--I'm not sure I'd want a threaded library call
running in a non-thread-aware app.
> I envisage having a natively implemented JDBC Connection passed to an
> init method in such a class.
>
> GCJ is perfect for this task because it has a native call interface,
> CNI, which is a seamless part of the class heirarchy.
>
> Once I've got something working I'll drop a line here.
Have fun! Sounds a neat idea.
-Doug
--
Let us cross over the river, and rest under the shade of the trees.
--T. J. Jackson, 1863
From | Date | Subject | |
---|---|---|---|
Next Message | Martijn van Oosterhout | 2002-01-23 02:22:53 | Re: detecting deadlocks |
Previous Message | Barry Lind | 2002-01-23 01:54:16 | Re: implemention of calls to stored procs. |