@@ -1801,3 +1801,275 @@ TIP 5: Have you checked our extensive FAQ?
18011801
18021802http://www.postgresql.org/users-lounge/docs/faq.html
18031803
1804+ From pgsql-hackers-owner+M16317=candle.pha.pa.us=pgman@postgresql.org Thu Dec 6 10:11:27 2001
1805+ Return-path: <pgsql-hackers-owner+M16317=candle.pha.pa.us=pgman@postgresql.org>
1806+ Received: from west.navpoint.com (west.navpoint.com [207.106.42.13])
1807+ by candle.pha.pa.us (8.11.6/8.10.1) with ESMTP id fB6FBQZ28795
1808+ for <pgman@candle.pha.pa.us>; Thu, 6 Dec 2001 10:11:26 -0500 (EST)
1809+ Received: from rs.postgresql.org (server1.pgsql.org [64.39.15.238] (may be forged))
1810+ by west.navpoint.com (8.11.6/8.10.1) with ESMTP id fB6FBPE23613
1811+ for <pgman@candle.pha.pa.us>; Thu, 6 Dec 2001 10:11:25 -0500 (EST)
1812+ Received: from postgresql.org (postgresql.org [64.49.215.8])
1813+ by rs.postgresql.org (8.11.6/8.11.6) with ESMTP id fB6F5MR55091
1814+ for <pgman@candle.pha.pa.us>; Thu, 6 Dec 2001 09:08:01 -0600 (CST)
1815+ (envelope-from pgsql-hackers-owner+M16317=candle.pha.pa.us=pgman@postgresql.org)
1816+ Received: from tiger.tigrasoft (fw.tigrasoft.hu [195.70.42.161])
1817+ by postgresql.org (8.11.3/8.11.4) with ESMTP id fB5JWMm92521;
1818+ Wed, 5 Dec 2001 14:32:26 -0500 (EST)
1819+ (envelope-from hornyakl@freemail.hu)
1820+ Received: from freemail.hu ([192.168.0.200])
1821+ by tiger.tigrasoft (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id UAA20333;
1822+ Wed, 5 Dec 2001 20:30:51 +0100
1823+ X-Authentication-Warning: tiger.tigrasoft: Host [192.168.0.200] claimed to be freemail.hu
1824+ Message-ID: <3C0E77F0.5030904@freemail.hu>
1825+ Date: Wed, 05 Dec 2001 20:39:28 +0100
1826+ From: Laszlo Hornyak <hornyakl@freemail.hu>
1827+ Reply-To: hornyakl@users.sourceforge.net
1828+ User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.4) Gecko/20010913
1829+ X-Accept-Language: hu, en-us
1830+ MIME-Version: 1.0
1831+ To: Barry Lind <barry@xythos.com>, pgsql-hackers@postgresql.org,
1832+ pgsql-jdbc@postgresql.org
1833+ Subject: Re: [HACKERS] [GENERAL] java stored procedures
1834+ References: <3C074DE4.9040905@freemail.hu> <3C0BE325.3020809@xythos.com> <3C0C937E.9000405@freemail.hu> <3C0CFD82.1030600@xythos.com> <3C0D219C.1090804@freemail.hu> <3C0D799D.4010808@xythos.com> <3C0DE382.1050400@freemail.hu> <3C0E5A23.7060701@xythos.com>
1835+ Content-Type: text/plain; charset=us-ascii; format=flowed
1836+ Content-Transfer-Encoding: 7bit
1837+ Precedence: bulk
1838+ Sender: pgsql-hackers-owner@postgresql.org
1839+ Status: OR
1840+
1841+ Barry Lind wrote:
1842+
1843+ >
1844+ > I also stopped cc'ing the general list, since this is getting too
1845+ > detailed for most of the members on that list.
1846+
1847+ Ok.
1848+
1849+ > Now to your mail:
1850+ >
1851+ > This seems like a reasonable approach and should work across different
1852+ > JVMs. It would probably be a good experiment to try this with the Sun
1853+ > or IBM jvm at some point to verify. What I was afraid of was that you
1854+ > were hacking the Kaffe code to perform the integration which would
1855+ > limit this solution to only using Kaffe.
1856+
1857+ I am sure they wont work the same way. I think I have a sun jdk 1.3.0-2,
1858+ so I will try to port it soon. The IBM implementation must wait I think
1859+ until january.
1860+
1861+ >
1862+ > Just a suggestion: PL/J might be a good name, since as you probably
1863+ > know it can't be called pl/java because of the trademark restrictions
1864+ > on the word 'java'.
1865+
1866+ Ok, you won, I do not read the licenses. From now it`s name is pl/j.
1867+ Isn`t 'j' too short for the name of the process that runns java? :)
1868+
1869+ >
1870+ > I am a little concerned about the stability and complexity of having
1871+ > this '-pizza' program be responsible for handling the calls on the
1872+ > java side. My concern is that this will need to be a multithreaded
1873+ > program since multiple backends will concurrently be needing to
1874+ > interact with multiple java threads through this one program. It
1875+ > might be simpler if each postgres process directly communicated to a
1876+ > java thread via a tcpip socket. Then the "-pizza" program would only
1877+ > need to be responsible for starting up the jvm and creating java
1878+ > threads and sockets for a postgres process (it would perform a similar
1879+ > role to postmaster for postgres client connections).
1880+
1881+ With good design we can solve stability problems. As much as I know, if
1882+ postmaster dies, the postgres server becomes unavailable, this looks the
1883+ same problem. I do not know if we realy need sockets. Anyway, if 'j'
1884+ dies, we can create a new one, and restart calculations. Some watchdog
1885+ functionality...
1886+ Doing thing with sockets need a lot of rework. It is the best time for
1887+ this, while there is not too much thing done.
1888+
1889+ >>>
1890+ >>>> -when java thread receives the signal, it reads the message(s) from
1891+ >>>> the queue, and starts some actions. When done it tells postgres
1892+ >>>> with a signal that it is ready, and it can come for its results.
1893+ >>>> This will be rewritten see below problems.
1894+ >>>
1895+ >>> Are signals the best way to accomplish this?
1896+ >>
1897+ >> I don`t know if it is the best, it is the only way I know :)
1898+ >> Do you know any other ways?
1899+ >>
1900+ > I don't know, but hopefully someone on the hackers list will chip in
1901+ > here with a comment.
1902+
1903+ After a first developement cycle (if my brain doesn`t burn down), the
1904+ signals can be replaced to a plugable communication interface I think.
1905+ So maybe we can use CORBA, or sockets, or something else. This will take
1906+ a lot of time.
1907+
1908+ > OK, so the same backend process that called the function gets messaged
1909+ > to process the sql. This should work. However it means you will need
1910+ > a special version of the jdbc driver that uses this shm+signals
1911+ > communication mechanism instead of what the current jdbc driver does.
1912+ > This is something I would be happy to help you with.
1913+
1914+
1915+ This is kind of you. :)
1916+ For this, I will have to finish the protocol of communication. I have to
1917+ learn Postgres enough, so I am not sure this will be done this weekend.
1918+ I have ideas, only time is needed to implement them or to recognize the
1919+ failures.
1920+
1921+ Thanks,
1922+ Laszlo Hornyak
1923+
1924+
1925+
1926+ ---------------------------(end of broadcast)---------------------------
1927+ TIP 4: Don't 'kill -9' the postmaster
1928+
1929+ From pgsql-hackers-owner+M16313=candle.pha.pa.us=pgman@postgresql.org Thu Dec 6 10:01:29 2001
1930+ Return-path: <pgsql-hackers-owner+M16313=candle.pha.pa.us=pgman@postgresql.org>
1931+ Received: from west.navpoint.com (west.navpoint.com [207.106.42.13])
1932+ by candle.pha.pa.us (8.11.6/8.10.1) with ESMTP id fB6F1RZ28000
1933+ for <pgman@candle.pha.pa.us>; Thu, 6 Dec 2001 10:01:27 -0500 (EST)
1934+ Received: from rs.postgresql.org (server1.pgsql.org [64.39.15.238] (may be forged))
1935+ by west.navpoint.com (8.11.6/8.10.1) with ESMTP id fB6F1OE19111
1936+ for <pgman@candle.pha.pa.us>; Thu, 6 Dec 2001 10:01:25 -0500 (EST)
1937+ Received: from postgresql.org (postgresql.org [64.49.215.8])
1938+ by rs.postgresql.org (8.11.6/8.11.6) with ESMTP id fB6EvtR54729
1939+ for <pgman@candle.pha.pa.us>; Thu, 6 Dec 2001 08:59:16 -0600 (CST)
1940+ (envelope-from pgsql-hackers-owner+M16313=candle.pha.pa.us=pgman@postgresql.org)
1941+ Received: from tiger.tigrasoft (fw.tigrasoft.hu [195.70.42.161])
1942+ by postgresql.org (8.11.3/8.11.4) with ESMTP id fB6EFfm64066;
1943+ Thu, 6 Dec 2001 09:15:41 -0500 (EST)
1944+ (envelope-from hornyakl@freemail.hu)
1945+ Received: from freemail.hu ([192.168.0.200])
1946+ by tiger.tigrasoft (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id PAA29094;
1947+ Thu, 6 Dec 2001 15:15:01 +0100
1948+ X-Authentication-Warning: tiger.tigrasoft: Host [192.168.0.200] claimed to be freemail.hu
1949+ Message-ID: <3C0F7F6B.2060605@freemail.hu>
1950+ Date: Thu, 06 Dec 2001 15:23:39 +0100
1951+ From: Laszlo Hornyak <hornyakl@freemail.hu>
1952+ Reply-To: hornyakl@users.sourceforge.net
1953+ User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.4) Gecko/20010913
1954+ X-Accept-Language: hu, en-us
1955+ MIME-Version: 1.0
1956+ To: Gunnar =?ISO-8859-1?Q?R=F8nning?= <gunnar@polygnosis.com>
1957+ cc: Barry Lind <barry@xythos.com>, pgsql-hackers@postgresql.org,
1958+ pgsql-jdbc@postgresql.org
1959+ Subject: Re: [HACKERS] [GENERAL] java stored procedures
1960+ References: <3C074DE4.9040905@freemail.hu> <3C0BE325.3020809@xythos.com><3C0C937E.9000405@freemail.hu> <3C0CFD82.1030600@xythos.com> <m2zo4wttp1.fsf@smaug.polygnosis.com>
1961+ Content-Type: text/plain; charset=ISO-8859-1; format=flowed
1962+ Content-Transfer-Encoding: 8bit
1963+ Precedence: bulk
1964+ Sender: pgsql-hackers-owner@postgresql.org
1965+ Status: OR
1966+
1967+ Hi!
1968+
1969+ Sorry, I have time only for short ansvers, it is company time :((.
1970+
1971+ Gunnar R�nning wrote:
1972+
1973+ >* Barry Lind <barry@xythos.com> wrote:
1974+ >|
1975+ >| possible problems with your strategy). Without knowing what exactly
1976+ >| you are thinking of doing it is difficult to comment.
1977+ >
1978+ >Agreed.
1979+ >
1980+ Ok, I will try to bring the code here before Monday, or at least some
1981+ pieces. It is full of hardcoded constants from my developement
1982+ environment. :(
1983+
1984+
1985+ >
1986+ >| I am very interested in hearing what your plans are for pl/java. I
1987+ >| think this is a very difficult project, but one that would be very
1988+ >| useful and welcome.
1989+ >
1990+ >I would very much like to hear about the plans myself.
1991+ >
1992+ I do not see so big difficulities yet, am I so lame? It won`t be easy,
1993+ realy, we should keep it simple, at least becouse of me.
1994+
1995+
1996+ thanks,
1997+ Laszlo Hornyak
1998+
1999+
2000+ ---------------------------(end of broadcast)---------------------------
2001+ TIP 3: if posting/reading through Usenet, please send an appropriate
2002+ subscribe-nomail command to majordomo@postgresql.org so that your
2003+ message can get through to the mailing list cleanly
2004+
2005+ From pgsql-hackers-owner+M16334=candle.pha.pa.us=pgman@postgresql.org Thu Dec 6 16:11:23 2001
2006+ Return-path: <pgsql-hackers-owner+M16334=candle.pha.pa.us=pgman@postgresql.org>
2007+ Received: from west.navpoint.com (west.navpoint.com [207.106.42.13])
2008+ by candle.pha.pa.us (8.11.6/8.10.1) with ESMTP id fB6LBLZ25078
2009+ for <pgman@candle.pha.pa.us>; Thu, 6 Dec 2001 16:11:22 -0500 (EST)
2010+ Received: from rs.postgresql.org (server1.pgsql.org [64.39.15.238] (may be forged))
2011+ by west.navpoint.com (8.11.6/8.10.1) with ESMTP id fB6LBMa12305
2012+ for <pgman@candle.pha.pa.us>; Thu, 6 Dec 2001 16:11:22 -0500 (EST)
2013+ Received: from postgresql.org (postgresql.org [64.49.215.8])
2014+ by rs.postgresql.org (8.11.6/8.11.6) with ESMTP id fB6L6wR66812
2015+ for <pgman@candle.pha.pa.us>; Thu, 6 Dec 2001 15:08:01 -0600 (CST)
2016+ (envelope-from pgsql-hackers-owner+M16334=candle.pha.pa.us=pgman@postgresql.org)
2017+ Received: from rh72.home.ee (adsl895.estpak.ee [213.168.23.133])
2018+ by postgresql.org (8.11.3/8.11.4) with ESMTP id fB6Kxtm98840;
2019+ Thu, 6 Dec 2001 15:59:55 -0500 (EST)
2020+ (envelope-from hannu@tm.ee)
2021+ Received: from tm.ee (localhost.localdomain [127.0.0.1])
2022+ by rh72.home.ee (8.11.6/8.11.6) with ESMTP id fB6I2pn02024;
2023+ Thu, 6 Dec 2001 23:02:52 +0500
2024+ Message-ID: <3C0FB2CB.90901@tm.ee>
2025+ Date: Thu, 06 Dec 2001 23:02:51 +0500
2026+ From: Hannu Krosing <hannu@tm.ee>
2027+ User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2
2028+ X-Accept-Language: et, en-us
2029+ MIME-Version: 1.0
2030+ To: hornyakl@users.sourceforge.net
2031+ cc: Gunnar =?ISO-8859-1?Q?R=F8nning?= <gunnar@polygnosis.com>,
2032+ Barry Lind
2033+ <barry@xythos.com>, pgsql-hackers@postgresql.org,
2034+ pgsql-jdbc@postgresql.org
2035+ Subject: Re: [HACKERS] [GENERAL] java stored procedures
2036+ References: <3C074DE4.9040905@freemail.hu> <3C0BE325.3020809@xythos.com><3C0C937E.9000405@freemail.hu> <3C0CFD82.1030600@xythos.com> <m2zo4wttp1.fsf@smaug.polygnosis.com> <3C0F7F6B.2060605@freemail.hu>
2037+ Content-Type: text/plain; charset=us-ascii; format=flowed
2038+ Content-Transfer-Encoding: 7bit
2039+ Precedence: bulk
2040+ Sender: pgsql-hackers-owner@postgresql.org
2041+ Status: OR
2042+
2043+ Laszlo Hornyak wrote:
2044+
2045+ >>
2046+ >> | I am very interested in hearing what your plans are for pl/java. I
2047+ >> | think this is a very difficult project, but one that would be very
2048+ >> | useful and welcome.
2049+ >>
2050+ >> I would very much like to hear about the plans myself.
2051+ >
2052+ > I do not see so big difficulities yet, am I so lame? It won`t be easy,
2053+ > realy, we should keep it simple, at least becouse of me.
2054+
2055+ Let me propose a very different approach to PL/J - use gcc-java and
2056+ figure out the problems
2057+ with (dynamic) compiling and dynamic linking.
2058+
2059+ This is an approach somewhat similar to .NET/C# that you first compile
2060+ things and then run instead
2061+ of trying to do both at the same time ;)
2062+
2063+ Oracle /may/ be doing something similar with their java stored
2064+ procedures, as they claim these to be "compiled".
2065+
2066+ -----------------
2067+ Hannu
2068+
2069+
2070+
2071+ ---------------------------(end of broadcast)---------------------------
2072+ TIP 3: if posting/reading through Usenet, please send an appropriate
2073+ subscribe-nomail command to majordomo@postgresql.org so that your
2074+ message can get through to the mailing list cleanly
2075+