From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Thomas Hallgren <thhal(at)mailblocks(dot)com> |
Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Permissions within a function |
Date: | 2004-12-17 22:44:37 |
Message-ID: | 24927.1103323477@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Thomas Hallgren <thhal(at)mailblocks(dot)com> writes:
> This is all about access to the java class images, i.e. the actual byte
> codes that make out the Java functions that will execute. Class files
> are normally grouped into archives called jar files (zip format
> essentially) and the SQL 2003 standard for server side Java defines
> stored procedures for loading, replacing, and removing such jars. I've
> implemented them as functions. A loaded jar is unpacked and stored as
> individual class files in a table.
AFAICS you are choosing to do things in the hardest possible way, on
the basis of completely unfounded suppositions about performance gains.
I recommend the KISS principle. Leave the jar files as jars and let the
Java runtime system manage them.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Mike G. | 2004-12-17 22:56:47 | Dump from cygwin directly to windows |
Previous Message | Thomas Hallgren | 2004-12-17 22:33:41 | Re: Permissions within a function |