Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
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: Mon, 30 Nov 2009 20:14:25 +0000
- Message-id: <20091130201425.GB1989@timac.local> <text/plain>
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.
- References:
- Initial refactoring of plperl.c - draft [PATCH]
- From: Tim Bunce
- Initial refactoring of plperl.c [PATCH]
- From: Tim Bunce
- Re: Initial refactoring of plperl.c [PATCH]
- From: Andrew Dunstan
- Re: Initial refactoring of plperl.c [PATCH]
- From: Tim Bunce
- Re: Initial refactoring of plperl.c [PATCH]
- From: Andrew Dunstan
- Initial refactoring of plperl.c - draft [PATCH]
- Prev by Date: Re: New VACUUM FULL
- Next by Date: Re: [PATCH 4/4] Add tests to dblink covering use of COPY TO FUNCTION
- Previous by thread: Re: Initial refactoring of plperl.c [PATCH]
- Next by thread: Syntax conflicts in frame clause
- Indexes: