Re: Initial refactoring of plperl.c [PATCH] - Mailing list pgsql-hackers

From Tim Bunce
Subject Re: Initial refactoring of plperl.c [PATCH]
Date
Msg-id 20091130201425.GB1989@timac.local
Whole thread Raw
In response to Re: Initial refactoring of plperl.c [PATCH]  (Andrew Dunstan <andrew@dunslane.net>)
List 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).

Tim.


pgsql-hackers by date:

Previous
From: Greg Smith
Date:
Subject: Re: New VACUUM FULL
Next
From: Greg Smith
Date:
Subject: Re: [PATCH 4/4] Add tests to dblink covering use of COPY TO FUNCTION