Skip site navigation (1) Skip section navigation (2)

Re: Initial refactoring of plperl.c [PATCH]

From: Tim Bunce <Tim(dot)Bunce(at)pobox(dot)com>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Tim Bunce <Tim(dot)Bunce(at)pobox(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Initial refactoring of plperl.c [PATCH]
Date: 2009-11-30 20:14:25
Message-ID: 20091130201425.GB1989@timac.local (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
On Mon, Nov 30, 2009 at 12:50:41PM -0500, Andrew Dunstan wrote:
> Tim Bunce wrote:
>> In summary, changing between multiplicity and non-multiplicity libperls
>> after building postgresql isn't safe or supported.
> OK, good. Are you adding a check at load time that the library loaded is 
> what we expect?

I won't think there's a need. The load will fail with undefined symbols
(or rather it will once the PL_exit_flags |= PERL_EXIT_DESTRUCT_END
change in the next patch gets added).


In response to

pgsql-hackers by date

Next:From: Greg SmithDate: 2009-11-30 20:14:35
Subject: Re: [PATCH 4/4] Add tests to dblink covering use of COPY TO FUNCTION
Previous:From: Greg SmithDate: 2009-11-30 20:10:43
Subject: Re: New VACUUM FULL

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group