Re: [HACKERS] JDBC and Perl compiling problems w/ postgresql-7.1rc4

Homayoun Yousefi'zadeh <homayounyz@home.com>

From: "Homayoun Yousefi'zadeh" <homayounyz@home.com>
To: Doug McNaught <doug@wireboard.com>
Cc: pgsql-general@postgresql.org, pgsql-hackers@postgresql.org
Date: 2001-04-10T17:06:08Z
Lists: pgsql-hackers, pgsql-general
> What you may not be aware of is that there are two places where Perl
> is used in the build.  One is the Perl client library (the 'Pg'
> module).  This should not require libperl.so as all it does is build a
> bog-standard extension module.
> 
> The other usage is for Perl as an embedded procedural language like
> PL/PGSQL.  In order to compile this you need a shared libperl.  It is
> not a "bug" in Postgres; it's simply what's required to embed the
> Perl interpreter into the backend.
> 
> If you just want the client lib, I think you can ignore the missing
> libperl.so and the client will be built just fine.  PL/Perl isn't that 
> useful right now anyhow since it doesn't have an interface to the
> backend's query mechanism.

Great information. Thanks.

The reason I need to compile w/ Perl
support turned on is what I am reading
in the README.rserv of the ERServer
available in contrib directory.
It says that the requirements are:

- PostgreSQL >= 7.0.X
   A separate Makefile is required for PostgreSQL 7.0.x and earlier
- Perl5 and the PostgreSQL perl interface

I am thinking that it only requires client lib as
the module compiles just fine. Can you confirm this please?

Regards,
HY