From: | "Florian G(dot) Pflug" <fgp(at)phlo(dot)org> |
---|---|
To: | Andreas Pflug <pgadmin(at)pse-consulting(dot)de> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jacob Rief <jacob(dot)rief(at)gmx(dot)at>, Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Writing triggers in C++ |
Date: | 2007-02-14 13:06:35 |
Message-ID: | 45D3095B.1090203@phlo.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Andreas Pflug wrote:
> Tom Lane wrote:
>> Jacob Rief <jacob(dot)rief(at)gmx(dot)at> writes:
>>
>>> I tried to write a trigger using C++.
>>>
>> That is most likely not going to work anyway, because the backend
>> operating environment is C not C++. If you dumb it down enough
>> --- no exceptions, no RTTI, no use of C++ library --- then it might
>> work,
> I can confirm that it does work this way.
I've written an aggregate function that uses c++ stl hashes, and it
seems to work pretty well. I'd think that using exceptions should be
fine, as long as you make sure to _always_ catch any exception that
might be thrown inside your own c++ code, and don't let it propagate
into backend code. STL allows you to specify custom allocator classes
as template parameters to hash, vector and the like. You can use that
to let STL allocate memory from the correct memory context.
greetings, Florian Pflug
From | Date | Subject | |
---|---|---|---|
Next Message | Pavan Deolasee | 2007-02-14 13:07:03 | Re: HOT for PostgreSQL 8.3 |
Previous Message | Andreas Pflug | 2007-02-14 12:00:52 | Re: Writing triggers in C++ |