Re: Problems using palloc in postgresql user C functions - Mailing list pgsql-novice

From John Gunther
Subject Re: Problems using palloc in postgresql user C functions
Date
Msg-id 3E7ACB2B.1020204@bucksvsbytes.com
Whole thread Raw
In response to Re: Problems using palloc in postgresql user C functions  (Joe Conway <mail@joeconway.com>)
List pgsql-novice
Thank you, gentlemen. With your kind assistance, I've succeeded in
creating my first C language pg function..

Joe Conway wrote:

> 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
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
>
>


pgsql-novice by date:

Previous
From: "Donald Tucker"
Date:
Subject: DBD::Pg installation difficulty during make test
Next
From: "Chr. Rossmanith"
Date:
Subject: age / timestamp