Re: late binding of shared libs for C functions

From: Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>, Geoff Winkless <pgsqladmin(at)geoff(dot)dj>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: late binding of shared libs for C functions
Date: 2018-06-12 14:05:16
Message-ID: 877en4t82y.fsf@news-spur.riddles.org.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>>>>> "Tom" == Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:

> Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> writes:
>> 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:

Tom> Error detection, ie did you spell the C symbol name correctly.

Right, but surely restoring a dump is not the place to be doing that
error check?

--
Andrew (irc:RhodiumToad)

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Darafei Komяpa Praliaskouski 2018-06-12 14:20:59 Re: late binding of shared libs for C functions
Previous Message Andrew Gierth 2018-06-12 14:03:32 Re: assert in nested SQL procedure call in current HEAD