Re: [HACKERS] pl/perl extension fails on Windows - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: [HACKERS] pl/perl extension fails on Windows
Date
Msg-id 6063dd4c-cd1e-d9d8-fa0d-3bddb1403c66@2ndQuadrant.com
Whole thread Raw
In response to Re: [HACKERS] pl/perl extension fails on Windows  (Dave Page <dpage@pgadmin.org>)
Responses Re: [HACKERS] pl/perl extension fails on Windows
List pgsql-hackers

On 07/12/2017 11:49 AM, Dave Page wrote:
>
>
> On Wed, Jul 12, 2017 at 4:35 PM, Tom Lane <tgl@sss.pgh.pa.us
> <mailto:tgl@sss.pgh.pa.us>> wrote:
>
>     Sandeep Thakkar <sandeep.thakkar@enterprisedb.com
>     <mailto:sandeep.thakkar@enterprisedb.com>> writes:
>     > I compiled PG 10 beta1/beta2 with "--with-perl" option on
>     Windows and the
>     > extension crashes the database.
>     > *src/pl/plperl/Util.c: loadable library and perl binaries are
>     mismatched
>     > (got handshake key 0A900080, needed 0AC80080)*
>
>     > This is seen with Perl 5.24 but not with 5.20, 5.16. What I
>     found is that
>     > the handshake function is added in Perl 5.21.x and probably that
>     is why we
>     > don't see this issue in earlier versions.
>
>     Well, we have various buildfarm machines running perls newer than
>     that,
>     eg, crake, with 5.24.1.  So I'd say there is something busted
>     about your
>     perl installation.  Perhaps leftover bits of an older version
>     somewhere?
>
>
> Well crake is a Fedora box - and we have no problems on Linux, only on
> Windows. 
>
>


Yeah, I have this on one of my Windows boxes, and haven't had time to
get to the bottom of it yet ;-(

Latest versions of ActivePerl don't ship with library descriptor files,
either, which is unpleasant.

cheers

andrew

-- 
Andrew Dunstan                https://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services




pgsql-hackers by date:

Previous
From: Jeff Janes
Date:
Subject: Re: [HACKERS] why not parallel seq scan for slow functions
Next
From: David Fetter
Date:
Subject: Re: [HACKERS] idea: custom log_line_prefix components besidesapplication_name