From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Kevin Murphy <murphy(at)genome(dot)chop(dot)edu> |
Cc: | PostgreSQL general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: STL problem in stored procedures |
Date: | 2005-10-25 14:44:08 |
Message-ID: | 13972.1130251448@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Kevin Murphy <murphy(at)genome(dot)chop(dot)edu> writes:
> Tom Lane wrote:
>> I think he needs to rewrite in C :-(. The backend is not C++ and I
>> fear it's unlikely that libc++ will play nicely as a dynamic add-on.
> It would be great if some C++/C guru could make a thorough analysis of
> C++ integration issues.
The main thing that scares me is lack of integration of C error handling
(setjmp/longjmp) with C++ error handling (catch/throw). In a
self-contained module you could perhaps avoid this by not using
catch/throw, but I don't think you get to ignore the issue if you are
using STL modules.
It *might* work to put a generic "catch/report via elog" handler around
each one of your entry-point functions. Haven't tried it.
This all assumes that libc++ can cooperate with, rather than try to
replace, libc in the first place. That would depend a lot on what
platform you are on --- I think it might work OK with modern glibc,
but my last experience with C++ was back when it wasn't so.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Fuhr | 2005-10-25 14:50:48 | Re: STL problem in stored procedures |
Previous Message | Kevin Murphy | 2005-10-25 14:24:53 | Re: STL problem in stored procedures |