From: J.Kraaijeveld at Askesis.nl (Joost Kraaijeveld)
Date: Fri, 14 Jul 2006 20:33:00 +0200
Subject: [Pljava-dev] zlib conflict on Debian AMD64 ???
In-Reply-To: <44B7D5BA.2060402@tada.se>
References: <1150963234.5987.11.camel@localhost> <449A52D8.4010208@tada.se>
	<1150971313.6071.6.camel@localhost> <449A9257.9040608@tada.se>
	<1150981643.6071.34.camel@localhost> <449A9836.1060909@tada.se>
	<1150982969.6071.39.camel@localhost>	<449AA178.5090806@tada.se>
	<449AABCB.3000403@tada.se>	<1150991211.6071.44.camel@localhost>
	<449ABC7F.4040806@tada.se> <44B7C76F.7020208@gmail.com>
	<44B7D5BA.2060402@tada.se>
Message-ID: <1152901980.6309.5.camel@localhost>

On Fri, 2006-07-14 at 19:34 +0200, Thomas Hallgren wrote:
> I also learned that this is no longer an issue in the in the coming 8.2 
> version of PostgreSQL since the backend no longer links with zlib. In 
> fact, there's no reason for it to link with zlib in 8.1 either. So a 
> safe workaround is to:
> 
> 1. preserve your current pg_dump/pg_restore (the only two programs that 
> use zlib)
> 2. configure using --without-zlib and rebuild and reinstall PostgreSQL
> 3. restore pg_dump/pg_restore
Alas, until I have a *working* "apt-get install" (yep, Debian and even
more simple users than developers ;-) )  I cannot use pl/java. 

I do have a working (and async!!!!) trigger mechanisme using
notify/listen an additional bean and JBoss, so for the moment I am
rescued. I even doubt if I want to abandon the async part if pl/java
works....


-- 
Groeten,

Joost Kraaijeveld
Askesis B.V.
Molukkenstraat 14
6524NB Nijmegen
tel: 024-3888063 / 06-51855277
fax: 024-3608416
web: www.askesis.nl