From: Tom Lane <tgl@sss.pgh.pa.us>
To: Pavel Raiskup <praiskup@redhat.com>
Cc: Robert Haas <robertmhaas@gmail.com>
Cc: pgsql-hackers@postgresql.org <pgsql-hackers@postgresql.org>
Cc: Devrim GÜNDÜZ <devrim@gunduz.org>
Subject: Re: plruby: rb_iterate symbol clash with libruby.so
Date: Wed, 07 Nov 2018 10:55:13 -0500
Message-ID: <12687.1541606113@sss.pgh.pa.us> (raw)
In-Reply-To: <1930142.Hb3bbeJPGd@nb.usersys.redhat.com>
References: <4738198.8KVIIDhgEB@nb.usersys.redhat.com>
<5127122.UsUPqPCgps@nb.usersys.redhat.com>
<25954.1541600731@sss.pgh.pa.us>
<1930142.Hb3bbeJPGd@nb.usersys.redhat.com>
Pavel Raiskup <praiskup@redhat.com> 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.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: tgl@sss.pgh.pa.us, praiskup@redhat.com, robertmhaas@gmail.com, devrim@gunduz.org
Subject: Re: plruby: rb_iterate symbol clash with libruby.so
In-Reply-To: <12687.1541606113@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox