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

From Andrew Dunstan
Subject Re: Initial refactoring of plperl.c [PATCH]
Date
Msg-id 4B11351E.6050001@dunslane.net
Whole thread Raw
In response to Initial refactoring of plperl.c [PATCH]  (Tim Bunce <Tim.Bunce@pobox.com>)
Responses Re: Initial refactoring of plperl.c [PATCH]
List pgsql-hackers

Tim Bunce wrote:
> - Changed MULTIPLICITY check from runtime to compiletime.
>     No loads the large Config module.
>   

ISTM the trouble with this is that it assumes that the library that we 
compile with is the same as the library loaded at runtime. But there is 
no guarantee of that at all.

Perhaps we could do this at library load time, so if it's preloaded in 
the postmaster we don't have to rerun the check for every backend.

Have you measured the cost involved here? Are we really saving that much?

cheers

andrew


pgsql-hackers by date:

Previous
From: Jeff Davis
Date:
Subject: Re: operator exclusion constraints
Next
From: Tom Lane
Date:
Subject: Re: Writeable CTE patch