On Feb 14, 2011, at 5:42 PM, Tom Lane wrote:
>> Remember also that not all modules out there on the net will have been
>> updated either, so we must be able to discuss "extension-izing a
>> module". (??)
>
> Right. So it seems like we ought to stick with more or less the
> existing terminology:
Simon Riggs writes:
> I would say that some modules are extensions, but not all. A standalone
> executable might be part of a module, but would not be an extension.
> Remember also that not all modules out there on the net will have been
> updated either, so we must be able to discuss "extension
On Mon, 2011-02-14 at 12:48 +0100, Dimitri Fontaine wrote:
> Tom Lane writes:
> > Appendix F (contrib.sgml and its subsidiary files) is pretty consistent
> > about using "module" to refer to a contrib, uh, module.
>
> I'm now thinking in those terms: the module is the shared object library
> that
Tom Lane writes:
> Hmm ... but what of contrib "modules" that don't build shared libraries
> at all --- pgbench and pg_upgrade for example?
>
> I think "shared library" is a perfectly fine term for that kind of
> object, and we don't need an alias for it anyway.
In my view, if there's no script,
Tom Lane writes:
> Appendix F (contrib.sgml and its subsidiary files) is pretty consistent
> about using "module" to refer to a contrib, uh, module.
I'm now thinking in those terms: the module is the shared object library
that the backend needs to dlopen(). The extension is the SQL level
object
Dimitri Fontaine writes:
> Another concern has to do with PLs. We said that with the dependency
> mechanism it would be good to have PLs be EXTENSIONs. But those are
> core provided extensions, one of them installed by default.
> If we make PLs extensions, we might also want to have CREATE LANG
Excerpts from Peter Eisentraut's message of sáb feb 12 04:44:10 -0300 2011:
> With the promotion of the contrib stuff, perhaps they should each get
> their own chapter in a new part.
+1 to this idea.
--
Álvaro Herrera
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consul
Dimitri Fontaine writes:
> Tom Lane writes:
>> Appendix F (contrib.sgml and its subsidiary files) is pretty consistent
>> about using "module" to refer to a contrib, uh, module.
> I'm now thinking in those terms: the module is the shared object library
> that the backend needs to dlopen(). The
