From: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
---|---|
To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
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-13 16:17:33 |
Message-ID: | 1334333853.4776.0.camel@localhost.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, 2012-04-12 at 12:28 +0300, Heikki Linnakangas wrote:
> 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.
>
Sounds good to me. I would love to see this happening in 9.2.
Thanks, Heikki.
--
Guillaume
http://blog.guillaume.lelarge.info
http://www.dalibo.com
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2012-04-13 16:33:06 | index-only scans vs. Hot Standby, round two |
Previous Message | Bruce Momjian | 2012-04-13 15:23:21 | 9.2 release notes, beta time? |