Thread: Re: [COMMITTERS] pgsql: Tidy up and refactor plperl.c.

Re: [COMMITTERS] pgsql: Tidy up and refactor plperl.c.

From
Tom Lane
Date:
adunstan@postgresql.org (Andrew Dunstan) writes:
> - Changed MULTIPLICITY check from runtime to compiletime.
>     No loads the large Config module.

[ squint... ]  I thought we'd decided that wasn't a good idea?
What happens if the libperl we load at runtime doesn't match what
we saw in the headers?
        regards, tom lane


Re: [COMMITTERS] pgsql: Tidy up and refactor plperl.c.

From
Robert Haas
Date:
On Fri, Jan 8, 2010 at 10:25 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> adunstan@postgresql.org (Andrew Dunstan) writes:
>> - Changed MULTIPLICITY check from runtime to compiletime.
>>     No loads the large Config module.
>
> [ squint... ]  I thought we'd decided that wasn't a good idea?
> What happens if the libperl we load at runtime doesn't match what
> we saw in the headers?

See:

http://archives.postgresql.org/pgsql-hackers/2009-11/msg01941.php

...Robert


Re: [COMMITTERS] pgsql: Tidy up and refactor plperl.c.

From
Tom Lane
Date:
Robert Haas <robertmhaas@gmail.com> writes:
> On Fri, Jan 8, 2010 at 10:25 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> [ squint... ] �I thought we'd decided that wasn't a good idea?

> http://archives.postgresql.org/pgsql-hackers/2009-11/msg01941.php

OK, I'd forgotten that ...
        regards, tom lane