Re: Problems using palloc in postgresql user C functions

From: Joe Conway <mail(at)joeconway(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: John Gunther <inbox(at)bucksvsbytes(dot)com>, pgsql-novice(at)postgresql(dot)org
Subject: Re: Problems using palloc in postgresql user C functions
Date: 2003-03-19 15:01:23
Message-ID: 3E788643.1020806@joeconway.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-novice

Tom Lane wrote:
> I'd suggest building one of the backend-extension modules in contrib/,
> and looking to see what commands get used to compile and link on your
> platform.
>

Another suggestion is to put your extension in a directory under
contrib, and copy and edit another contrib's Makefile. They are pretty
simple, e.g. let's say your library is called foo, and you put foo.c,
foo.h, and foo.sql.in in contrib/foo. Your Makefile would look like:

8<-------------------------------------
subdir = contrib/foo
top_builddir = ../..
include $(top_builddir)/src/Makefile.global

MODULES = foo
DATA_built = foo.sql

include $(top_srcdir)/contrib/contrib-global.mk
8<-------------------------------------

Now you can do (from contrib/foo):

make
make install
psql myfoodatabase < foo.sql

to build and install foo.so.

For more info on the contrib Makefile layout and variables, look at the
comments in contrib/contrib-global.mk

Joe

In response to

Responses

Browse pgsql-novice by date

  From Date Subject
Next Message Patrick Hatcher 2003-03-19 18:00:23 Re: Problems with copy
Previous Message Tom Lane 2003-03-19 14:22:46 Re: Problems using palloc in postgresql user C functions