Re: late binding of shared libs for C functions - Mailing list pgsql-hackers

From Andrew Gierth
Subject Re: late binding of shared libs for C functions
Date
Msg-id 87fu1stbqw.fsf@news-spur.riddles.org.uk
Whole thread Raw
In response to Re: late binding of shared libs for C functions  (Andrew Dunstan <andrew.dunstan@2ndquadrant.com>)
Responses Re: late binding of shared libs for C functions
Re: late binding of shared libs for C functions
List pgsql-hackers
>>>>> "Andrew" == Andrew Dunstan <andrew.dunstan@2ndquadrant.com> writes:

 Andrew> Perhaps something like NO CHECK would meet the case, i.e. we're
 Andrew> not checking the link at function creation time.

The real question is why check_function_bodies doesn't cover this;
there's a comment in fmgr_c_validator that this is deliberate, but it's
rather unclear what the advantage is supposed to be:

 * It'd be most consistent to skip the check if !check_function_bodies,
 * but the purpose of that switch is to be helpful for pg_dump loading,
 * and for pg_dump loading it's much better if we *do* check.

-- 
Andrew (irc:RhodiumToad)


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: late binding of shared libs for C functions
Next
From: Andrew Dunstan
Date:
Subject: Re: late binding of shared libs for C functions