| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
|---|---|
| To: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Why can't I use pgxs to build a plpgsql plugin? |
| Date: | 2012-04-12 09:28:51 |
| Message-ID: | 4F86A053.6030202@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 08.04.2012 11:59, Guillaume Lelarge wrote:
> Hi,
>
> I recently wrote a plpgsql plugin. I wanted to enable the use of pgxs,
> to make it easier to compile the plugin, but I eventually found that I
> can't do that because the plpgsql.h file is not available in the include
> directory.
>
> I'm wondering if we shouldn't put the header files of plpgsql source
> code in the include directory. It would help compiling the PL/pgsql
> debugger, and profiler (and of course my own plugin).
Yep, I just bumped into this myself, while trying to make pldebugger
module compilable with pgxs.
> There could be a good reason which would explain why we can't (or don't
> want to) do this, but I don't see it right now.
Me neither, except a general desire to keep internals hidden. I propose
the attached.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| Attachment | Content-Type | Size |
|---|---|---|
| install-plpgsql-header-file-1.patch | text/x-diff | 1016 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2012-04-12 09:59:25 | docs: WITH queries and VALUES |
| Previous Message | Magnus Hagander | 2012-04-12 05:59:33 | Re: Last gasp |