From: | Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: transforms |
Date: | 2013-03-13 16:54:33 |
Message-ID: | m2li9rnsty.fsf@2ndQuadrant.fr |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> At run time, this will sort itself out, because all the required modules
> will be loaded. The problem is when you create the "glue" extension and
> haven't invoked any code from any of the dependent extension in the
> session. Abstractly, the possible solutions are either not to check the
> functions when the extension is created (possibly settable by a flag) or
> to somehow force a load of all dependent extensions when the new
> extension is created. (I say extension here even though dynamically
> loadable modules are attached to functions, which makes this even more
> confusing.)
I think CREATE EXTENSION should be LOADing all distinct modules
referenced from all required extensions functions. It does sound easy
enough to code, and I can't imagine why we would want to not do that.
Regards,
--
Dimitri Fontaine
http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2013-03-13 17:09:45 | Re: Enabling Checksums |
Previous Message | Gavin Flower | 2013-03-13 16:51:42 | Re: Duplicate JSON Object Keys |