Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1YnBqJ-0001x0-Gg for pgsql-hackers@arkaria.postgresql.org; Tue, 28 Apr 2015 20:10:55 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1YnBqI-00041k-NK for pgsql-hackers@arkaria.postgresql.org; Tue, 28 Apr 2015 20:10:54 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1YnBqH-00041Q-1d for pgsql-hackers@postgresql.org; Tue, 28 Apr 2015 20:10:53 +0000 Received: from relay3-d.mail.gandi.net ([2001:4b98:c:538::195]) by makus.postgresql.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84) (envelope-from ) id 1YnBqE-0002SJ-Bo for pgsql-hackers@postgresql.org; Tue, 28 Apr 2015 20:10:51 +0000 Received: from mfilter16-d.gandi.net (mfilter16-d.gandi.net [217.70.178.144]) by relay3-d.mail.gandi.net (Postfix) with ESMTP id F253CA80B6; Tue, 28 Apr 2015 22:10:46 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at mfilter16-d.gandi.net Received: from relay3-d.mail.gandi.net ([217.70.183.195]) by mfilter16-d.gandi.net (mfilter16-d.gandi.net [10.0.15.180]) (amavisd-new, port 10024) with ESMTP id UlIdU1oCeoiD; Tue, 28 Apr 2015 22:10:45 +0200 (CEST) X-Originating-IP: 98.27.58.255 Received: from [192.168.10.146] (cpe-98-27-58-255.nc.res.rr.com [98.27.58.255]) (Authenticated sender: adsend@dunslane.net) by relay3-d.mail.gandi.net (Postfix) with ESMTPSA id 19655A80BB; Tue, 28 Apr 2015 22:10:43 +0200 (CEST) Message-ID: <553FE942.4040604@dunslane.net> Date: Tue, 28 Apr 2015 16:10:42 -0400 From: Andrew Dunstan User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: Michael Paquier CC: Peter Eisentraut , Tom Lane , Tom Lane , PostgreSQL-development Subject: Re: [COMMITTERS] pgsql: Add transforms feature References: <18844.1430066190@sss.pgh.pa.us> <553E29B5.9000102@gmx.net> <553ECC34.2090104@dunslane.net> <553EDA8A.9090806@dunslane.net> <553FAC70.2070309@dunslane.net> <553FAF6D.3070703@dunslane.net> In-Reply-To: <553FAF6D.3070703@dunslane.net> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -2.6 (--) 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 04/28/2015 12:03 PM, Andrew Dunstan wrote: > > [switching to -hackers] > > On 04/28/2015 11:51 AM, Andrew Dunstan wrote: >> >> On 04/28/2015 09:04 AM, Michael Paquier wrote: >>> On Tue, Apr 28, 2015 at 10:01 AM, Michael Paquier >>> wrote: >>>> On Tue, Apr 28, 2015 at 9:55 AM, Andrew Dunstan wrote: >>>>> w.r.t MSVC builds, it looks like we need entries in >>>>> $contrib_extraincludes >>>>> in src/tools/msvc/Mkvcbuild.pm at the very least. >>>> If our goal is to put back to green the Windows nodes as quick as >>>> possible, we could bypass their build this way , and we'll >>>> additionally need to update the install script and >>>> vcregress.pl/contribcheck to bypass those modules accordingly. Now I >>>> don't think that we should make the things produced inconsistent. >>> OK, attached are two patches to put back the buildfarm nodes using >>> MSVC to green >>> - 0001 adds support for build and installation of the new transform >>> modules: hstore_plperl, hstore_plpython and ltree_plpython. Note that >>> this patch is enough to put back the buildfarm to a green state for >>> MSVC, but it disables the regression tests for those modules, >>> something addressed in the next patch... >>> - 0002 adds support for regression tests for the new modules. The >>> thing is that we need to check the major version version of Python >>> available in configuration and choose what are the extensions to >>> preload before the tests run. It is a little bit hacky... But it has >>> the merit to work, and I am not sure we could have a cleaner solution >>> by looking at the Makefiles of the transform modules that use >>> currently conditions based on $(python_majorversion). >>> Regards, >> >> >> I have pushed the first of these with some tweaks. >> >> I'm looking at the second. >> >> > > > Regarding this second patch - apart from the buggy python version test > which I just fixed in the first patch, I see this: > > + if ($pyver eq "2") > + { > + push @opts, "--load-extension=plpythonu"; > + push @opts, '--load-extension=' . $module . 'u'; > + } > > > But what do we do for Python3? > > Do we actually have a Windows machine building with Python3? The answer seems to be "probably not". When I tried enabling this with bowerbird I got a ton of errors like these: plpy_cursorobject.obj : error LNK2001: unresolved external symbol PyObject_SelfIter [C:\prog\bf\root\HEAD\pgsql\plpython3.vcxproj] plpy_cursorobject.obj : error LNK2019: unresolved external symbol __imp_PyType_Ready referenced in function PLy_cursor_init_type [C:\prog\bf\root\HEAD\pgsql\plpython3.vcxproj] Something else to fix I guess. cheers andrew -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers