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 1gKOm8-0003zB-In for pgsql-hackers@arkaria.postgresql.org; Wed, 07 Nov 2018 14:25:44 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gKOm3-0002FA-VD for pgsql-hackers@arkaria.postgresql.org; Wed, 07 Nov 2018 14:25:39 +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.89) (envelope-from ) id 1gKOm3-0002F3-Nx for pgsql-hackers@lists.postgresql.org; Wed, 07 Nov 2018 14:25:39 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1gKOm1-0007up-6W for pgsql-hackers@postgresql.org; Wed, 07 Nov 2018 14:25:39 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id wA7EPVok025955; Wed, 7 Nov 2018 09:25:31 -0500 From: Tom Lane To: Pavel Raiskup 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 In-reply-to: <5127122.UsUPqPCgps@nb.usersys.redhat.com> References: <4738198.8KVIIDhgEB@nb.usersys.redhat.com> <22881.1541515786@sss.pgh.pa.us> <28762.1541528901@sss.pgh.pa.us> <5127122.UsUPqPCgps@nb.usersys.redhat.com> Comments: In-reply-to Pavel Raiskup message dated "Wed, 07 Nov 2018 13:55:57 +0100" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <25953.1541600731.1@sss.pgh.pa.us> Date: Wed, 07 Nov 2018 09:25:31 -0500 Message-ID: <25954.1541600731@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Pavel Raiskup writes: > On Tuesday, November 6, 2018 7:28:21 PM CET Tom Lane wrote: >> Done. I realized that the immediate problem, rb_iterate(), was only >> added as of PG v10, which may explain why we hadn't heard complaints >> about this till now. So I've made the change only as far back as v10. > The 'rb_iterate' seems to exist at least in REL9_2_STABLE branch, so it is > probably much older. Oh! Hmm ... I think I jumped to conclusions when the part of my patch that touched struct RBTreeIterator failed to apply. But you're right, rb_iterate has been there since 9.0 now that I look more carefully. So we really ought to back-patch further. However: > That > said, I'm still not sure how this could work before ... Maybe it has not > been working for some time. 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? regards, tom lane