Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1da0yF-0006jQ-UB for pgsql-hackers@arkaria.postgresql.org; Tue, 25 Jul 2017 14:38:00 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1da0yF-000564-CI for pgsql-hackers@arkaria.postgresql.org; Tue, 25 Jul 2017 14:37:59 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1da0yE-00055t-NF for pgsql-hackers@postgresql.org; Tue, 25 Jul 2017 14:37:58 +0000 Received: from mail-qt0-x22a.google.com ([2607:f8b0:400d:c0d::22a]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1da0yA-0001JO-8Y for pgsql-hackers@postgresql.org; Tue, 25 Jul 2017 14:37:57 +0000 Received: by mail-qt0-x22a.google.com with SMTP id p3so27526024qtg.2 for ; Tue, 25 Jul 2017 07:37:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=from:subject:to:cc:references:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding:content-language; bh=KqkrnD5vVjkBNy7ptZ3I3TaAcMDQP3Jv1eAEkELIHkA=; b=JoLLo9g7mNcsWomscw510UPgs7pRY7DvPH81oQA1lMZ7cf7HBH4iGr1uYkVWkFQOxL 1s07vjCqtwEmFe16Mn35VFm8qi9VvB4to7ROgGh8ZYoA0j6a4VqqeWLk26SRck7hpaCC poV2d1JQYOEqN0PcA3ap6YAnMI+W9m4liAGtvAjuXfYJufYDjsNnY9tv5rFrkiwktpVU hmb03zSGCEO/PfrjsRPEjeKsMXahBhiArtMLMV1bDLrpuWCs4oxokGYz67YB9uyMsXj/ KZwmt05gs0f4AMLBC0T5xDkhSlVpGSj9LFEgox4WDbGHNadrqBvrJPO8DS+vKFW1X3Y3 b6bg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:subject:to:cc:references:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=KqkrnD5vVjkBNy7ptZ3I3TaAcMDQP3Jv1eAEkELIHkA=; b=Kx/66+KhF+UoPX0UsOmZBb4SFnvy8riI2ZQUjfdYaElgIagC1sxrUVJYxyxnuSYsCc CaFUmWY+pRk5ywV42R0LeU0nrty0XtmV94qS2KatWieQH99XiorbWTkmqsXR9cQIhBqZ n3Md9iu/FlE3GGYsIg9YQh/rbTEJWNRHKHr5eNtfgkKIfituITc4YryF3aa/3Dx8OLLe 6g/K8FOwQjXdso/QwYsnF1YwJcPwh5q4u9QI8hjVNmlLOh81f3CA9lodTcPkc2QPUwfR 9wgZun8LVzvoAwA+tL1adZzF72dXF/ydzDzMYnuXrc2GDVIcnMaBJ9Ojwj+p31srRcPn CmPw== X-Gm-Message-State: AIVw111vjc/VMJhISKN198jfVdUs9Ko26tzZPAnUvmXeBxW7WkwnNaXD wOXcDgcYmG2EuSqd88TAYF9meK4KecycoDfxkYYdg5d3ml6d+Jllm1o/3GbzhcI36WRy4SOQPJa JdEu3c9gLbZpB0VXd3C4JJbeAddWd//tjVK5kYg9y5UX+S+m4Kwd4xmiESJOSewfvMhlAgRCZ7b jUmDKW X-Received: by 10.237.63.45 with SMTP id p42mr24287810qtf.320.1500993471883; Tue, 25 Jul 2017 07:37:51 -0700 (PDT) Received: from [192.168.10.146] ([98.122.175.38]) by smtp.gmail.com with ESMTPSA id d206sm2919322qke.81.2017.07.25.07.37.51 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 25 Jul 2017 07:37:51 -0700 (PDT) From: Andrew Dunstan X-Google-Original-From: Andrew Dunstan Subject: Re: pl/perl extension fails on Windows To: Amit Kapila , Noah Misch Cc: Tom Lane , Ashutosh Sharma , Dave Page , Sandeep Thakkar , "pgsql-hackers@postgresql.org" References: <6063dd4c-cd1e-d9d8-fa0d-3bddb1403c66@2ndQuadrant.com> <184f1fb9-dfa2-ef2d-024b-7933486e018a@2ndQuadrant.com> <16093.1499956602@sss.pgh.pa.us> <7480.1499965218@sss.pgh.pa.us> <30585.1500480763@sss.pgh.pa.us> <32468.1500498091@sss.pgh.pa.us> <20170724062838.GB2284350@rfd.leadboat.com> Message-ID: <21dc1689-94e9-7af7-e8a2-c78b0563fff6@2ndQuadrant.com> Date: Tue, 25 Jul 2017 10:37:50 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Content-Language: en-MW List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org On 07/25/2017 08:58 AM, Amit Kapila wrote: > > I think the real question is where do we go from here. Ashutosh has > proposed a patch up-thread based on a suggestion from Andrew, but it > is not clear if we want to go there as that seems to be bypassing > handshake mechanism. The other tests and analysis seem to indicate > that the new version Perl binaries on Windows are getting built with > flags that are incompatible with what we use for plperl and it is not > clear why perl is using those flags. Do you think we can do something > at our end to make it work or someone should check with Perl community > about it? > No amount of checking with the Perl community is likely to resolve this quickly w.r.t. existing releases of Perl. We seem to have a choice either to abandon, at least temporarily, perl support on Windows for versions of perl >= 5.20 (I think) or adopt the suggestion I made. It's not a complete hack - it's something at least somewhat blessed in perl's XSUB.h: /* dXSBOOTARGSNOVERCHK has no API in xsubpp to choose it so do #undef dXSBOOTARGSXSAPIVERCHK #define dXSBOOTARGSXSAPIVERCHK dXSBOOTARGSNOVERCHK */ Note that on earlier versions of perl we got by without this check for years without any issue or complaint I recall hearing of. If we don't adopt this I would not be at all surprised to see Windows packagers adopt it anyway. cheers andrew -- Andrew Dunstan https://www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers