Ken,
I made some further investigation concerning this. I knew that Sun has addressed this bug
long ago. Now I found two bug reports. Both bugs are marked as fixed/closed which make me
curious. What Java version are you using when you encounter this problem?
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4953050
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=5077725
I also managed to locate an old discussion around this that might be of interest:
http://archives.postgresql.org/pgsql-hackers/2004-09/msg00715.php
It indicates that the zlib is perhaps not needed at all in the backend. It's there because
of "lazy" management of needed libraries.
Regards,
Thomas Hallgren
Kenneth Marshall wrote:
> On Thu, Feb 02, 2006 at 12:29:39PM -0800, Josh Berkus wrote:
>> Thomas,
>>
>>> And don't forget to mention
>>> PL/Java ;-)
>> You'll be happy to know that the analyst had a specific question about java
>> procedural support.
>>
>> BTW, what happened to the discussion of moving PL/java into core for 8.2?
>>
>> --
>> --Josh
>>
> Josh,
>
> We tried to include PL/java in our standard build, but the version of
> the zlib library in the JVM is ancient and the incompatibility would
> cause the DB to crash. Until we can get a JVM built against a current
> library from Sun I think it would be a bad idea to have PL/java in
> the core.
>
> Ken
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faq
>