Re: [HACKERS] "Extension" versus "module"

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgreSQL(dot)org, pgsql-docs(at)postgreSQL(dot)org
Subject: Re: [HACKERS] "Extension" versus "module"
Date: 2011-02-15 01:36:32
Message-ID: 1297733792.1747.18295.camel@ebony
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs pgsql-hackers

On Mon, 2011-02-14 at 12:48 +0100, Dimitri Fontaine wrote:
> Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> 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 that wraps all its components.

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-izing a
module". (??)

--
Simon Riggs http://www.2ndQuadrant.com/books/
PostgreSQL Development, 24x7 Support, Training and Services

In response to

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message Tom Lane 2011-02-15 01:42:40 Re: [HACKERS] "Extension" versus "module"
Previous Message Tom Lane 2011-02-14 16:32:52 Re: [HACKERS] "Extension" versus "module"

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2011-02-15 01:42:40 Re: [HACKERS] "Extension" versus "module"
Previous Message Tom Lane 2011-02-15 01:36:03 Re: sepgsql contrib module