From: | wieck(at)debis(dot)com (Jan Wieck) |
---|---|
To: | lamar(dot)owen(at)wgcr(dot)org (Lamar Owen) |
Cc: | pgsql-hackers(at)postgreSQL(dot)org, pgsql-ports(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] SPI Headers -- RPM distribution |
Date: | 1999-12-20 19:47:19 |
Message-ID: | m1208m7-0003kHC@orion.SAPserv.Hamburg.dsh.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-ports |
>
> Ok, thanks to Oliver and others, I think I may have a handle on which
> header files to include in the postgresql-devel RPM for the ability to
> compile backend modules.
>
> So, I'm going to put these headers under /usr/include/pgsql/backend.
>
> Any objections or comments?
I'm not totally sure, but IIRC the dependency list was the
one of spi.c, no?
If so, it's IMHO wrong. A user written module doesn't need
anything, spi.c needs (especially the parts included by
spi_priv.h). SPI hides many internals by making the prepared
plan an opaque object (void *).
Jan
--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#========================================= wieck(at)debis(dot)com (Jan Wieck) #
From | Date | Subject | |
---|---|---|---|
Next Message | Goran Thyni | 1999-12-20 20:29:06 | Re: [HACKERS] Re: QUESTION: Replication |
Previous Message | Lamar Owen | 1999-12-20 19:37:33 | SPI Headers -- RPM distribution |
From | Date | Subject | |
---|---|---|---|
Next Message | Brook Milligan | 1999-12-20 20:41:12 | Re: [HACKERS] SPI Headers -- RPM distribution |
Previous Message | Lamar Owen | 1999-12-20 19:37:33 | SPI Headers -- RPM distribution |