Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1gKQLM-0000xR-5b for pgsql-hackers@arkaria.postgresql.org; Wed, 07 Nov 2018 16:06:12 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gKQLK-0002Ec-OJ for pgsql-hackers@arkaria.postgresql.org; Wed, 07 Nov 2018 16:06:10 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1gKQLK-0002EG-DQ for pgsql-hackers@lists.postgresql.org; Wed, 07 Nov 2018 16:06:10 +0000 Received: from mx1.redhat.com ([209.132.183.28]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1gKQLH-0004fw-CM for pgsql-hackers@postgresql.org; Wed, 07 Nov 2018 16:06:08 +0000 Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 8C45980F88; Wed, 7 Nov 2018 16:06:05 +0000 (UTC) Received: from nb.usersys.redhat.com (unknown [10.43.2.86]) by smtp.corp.redhat.com (Postfix) with ESMTP id 8461C60C60; Wed, 7 Nov 2018 16:06:04 +0000 (UTC) From: Pavel Raiskup To: Tom Lane Cc: Robert Haas , "pgsql-hackers@postgresql.org" , Devrim =?ISO-8859-1?Q?G=DCND=DCZ?= Subject: Re: plruby: rb_iterate symbol clash with libruby.so Date: Wed, 07 Nov 2018 17:06:01 +0100 Message-ID: <2108690.PGVSR67BWN@nb.usersys.redhat.com> In-Reply-To: <12687.1541606113@sss.pgh.pa.us> References: <4738198.8KVIIDhgEB@nb.usersys.redhat.com> <1930142.Hb3bbeJPGd@nb.usersys.redhat.com> <12687.1541606113@sss.pgh.pa.us> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Scanned-By: MIMEDefang 2.79 on 10.5.11.12 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.27]); Wed, 07 Nov 2018 16:06:05 +0000 (UTC) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Wednesday, November 7, 2018 4:55:13 PM CET Tom Lane wrote: > Pavel Raiskup writes: > > On Wednesday, November 7, 2018 3:25:31 PM CET Tom Lane wrote: > >> Yeah, I'm now mighty confused about this as well. PL/Ruby is pretty old > >> too, so how come nobody noticed this before? Is its rb_iterate call in > >> someplace that hardly gets any use? > > > ... I reproduced this by trigger function from tests/plt test-case > > on the first try, more info and related fixes in [1]. But it is truth > > that we haven't run the test-suite for RPM builds so far. > > Might the reason be that nobody used plruby at all for a very long time? > > I'm starting to think that. I just browsed through the code of plruby, > and while I don't know that language at all, there are rb_iterate calls > in places that look like they'd be hard to avoid in typical use. > > The fact that the upstream git repo hasn't been touched in nine years > doesn't exactly indicate a lively project, either :-( > > If you guys want to pursue this, I'll finish up the back-patch, but I > wonder if we're just wasting our time. FWIW, I plan to help with fixing the plruby project, but to be honest - I still think that the code can be fixed to not use rb_iterate() anyways. So back-patch is not needed by me - and certainly not now. Pavel