| From: | Andy Shellam <andy(at)andycc(dot)net> |
|---|---|
| To: | Sean Davis <sdavis2(at)mail(dot)nih(dot)gov> |
| Cc: | pgsql-interfaces(at)postgresql(dot)org |
| Subject: | Re: pl/perl library question |
| Date: | 2006-06-24 15:04:48 |
| Message-ID: | 449D5490.7010703@andycc.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-interfaces |
This is true, although in an ideal solution, the developers wouldn't be
using multiple versions of perl in different places, so this wouldn't be
an issue!
Sean Davis wrote:
>
> ----- Original Message ----- From: "Andy Shellam" <andy(at)andycc(dot)net>
> To: <kevin(at)kevinkempterllc(dot)com>
> Cc: <pgsql-interfaces(at)postgresql(dot)org>
> Sent: Saturday, June 24, 2006 8:13 AM
> Subject: Re: [INTERFACES] pl/perl library question
>
>
>> I've not done a lot with Perl, so can't comment on anything specific
>> to do with Perl, however, as an obvious "quick fix", can you symlink
>> the actual location of your library to the location Perl is looking in?
>
> The better fix (and I'm no expert, either) is probably to make sure
> that the perl that pg is using is the same perl under which you
> install packages. It wasn't clear from the OP that this was the case.
>
> Sean
>
> !DSPAM:14,449d50d8256841247620461!
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Matteo Traina | 2006-06-27 11:47:14 | jdbc windows |
| Previous Message | Sean Davis | 2006-06-24 14:48:44 | Re: pl/perl library question |