Re: late binding of shared libs for C functions

From: Darafei "Komяpa" Praliaskouski <me(at)komzpa(dot)net>
To: Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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:20:59
Message-ID: CAC8Q8tJ-WDdHRhniTFABZJmKX_+m+ADVEDQtgCW2qGAi9JX=sQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>
> >> 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?
>

Similar check also happens on pg_upgrade in link mode. It would be more
useful to get it to attempt to upgrade the extension if there is absent
function or absent library error.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jonathan S. Katz 2018-06-12 14:21:29 Re: pg_config.h.win32 missing a set of flags from pg_config.h.in added in v11 development
Previous Message Andrew Gierth 2018-06-12 14:05:16 Re: late binding of shared libs for C functions