Re: PG Extensions: Must be statically linked? - Mailing list pgsql-hackers

From Mark Dilger
Subject Re: PG Extensions: Must be statically linked?
Date
Msg-id 44088A4D.1060104@markdilger.com
Whole thread Raw
In response to Re: PG Extensions: Must be statically linked?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: PG Extensions: Must be statically linked?  (Andreas Seltenreich <andreas+pg@gate450.dyndns.org>)
List pgsql-hackers
Tom Lane wrote:
> My concern about how nicely libstdc++ will play in the backend
> environment still stands though.

I have had the same concern, though never any hard evidence of a problem.  If 
the C++ functions are wrapped with "extern C", and all exceptions caught 
(perhaps converted into error numbers which are then returned from the wrapper 
functions to the plain-C calling functions), are there any remaining known 
problems?  I have often considered making a C++ allocator which wrapped palloc 
and pfree, so that I could then use the STL within the backend...

Has anyone tried this?

mark


pgsql-hackers by date:

Previous
From: Stephan Szabo
Date:
Subject: Re: Foreign keys for non-default datatypes
Next
From: Tom Lane
Date:
Subject: Re: ipcclean in 8.1 broken?