Re: late binding of shared libs for C functions

From: Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>
To: Geoff Winkless <pgsqladmin(at)geoff(dot)dj>, chris(at)chrullrich(dot)net
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: late binding of shared libs for C functions
Date: 2018-06-12 15:15:38
Message-ID: 955d28fd-8273-ae20-9924-51ed4028cef3@2ndQuadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 06/12/2018 11:09 AM, Geoff Winkless wrote:
> On Tue, 12 Jun 2018 at 15:44, Christian Ullrich <chris(at)chrullrich(dot)net> wrote:
>>> I did wonder about "NO CHECK" but wasn't sure if having two words
>>> would make the parser change more complex.
>> DEFERRED?
> That's a good shout. I wouldn't mind either of those choices.
>
> So can I assume at least that no-one has an objection to the general principle?
>
> I don't currently have a PG dev environment set up so it's non-trivial
> for me to implement, which I'm ok with but not if I'm just wasting my
> (and everyone else's) time :)
>

I would wait a little while. The idea's only been floated for a few hours.

cheers

andrew

--
Andrew Dunstan https://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2018-06-12 15:25:37 Re: assert in nested SQL procedure call in current HEAD
Previous Message Geoff Winkless 2018-06-12 15:09:29 Re: late binding of shared libs for C functions