From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
---|---|
To: | "Carl E(dot) McMillin" <carlymac(at)earthlink(dot)net> |
Cc: | PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: postgresql extension API proof of concept |
Date: | 2004-05-22 08:59:31 |
Message-ID: | Pine.LNX.4.58.0405221028430.1804@sablons.cri.ensmp.fr |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Dear Carl,
> What is the purpose of the extension api in simple terms; what is it FOR?
> What does it DO?
Thanks for this perfectly legitimate question, as my mail was not very
easy to understand without the context.
The aim is to provide a compilation infrastructure to external modules
(that is things that are not distributed with the core of postgresql but
must be integrated to it, such as new types or new functions which deal
with backend informations).
The idea is that any external module could have a very simple makefile and
reuse all of postgresql build infrastructure (makefiles, scripts...) to
be build against an already installed postgresql.
I hope this is clearer,
have a nice day,
--
Fabien Coelho - coelho(at)cri(dot)ensmp(dot)fr
From | Date | Subject | |
---|---|---|---|
Next Message | Fabien COELHO | 2004-05-22 09:01:55 | Re: add server include files to default installation? |
Previous Message | Christopher Kings-Lynne | 2004-05-22 07:52:44 | Re: Database variables when copying a database |