Re: server-side extension in c++

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, Igor <igor(at)carcass(dot)ath(dot)cx>, pgsql-general(at)postgresql(dot)org
Subject: Re: server-side extension in c++
Date: 2010-06-01 13:58:24
Message-ID: 2114.1275400704@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> writes:
> On 01/06/10 11:05, Tom Lane wrote:
>> I'd be interested to see a section like this written by someone who'd
>> actually done a nontrivial C++ extension and lived to tell the tale.

> I can't speak up there - my own C++/Pg backend stuff has been fairly
> trivial, and has been where I can maintain a fairly clean separation of
> the C++-exposed and the Pg-backend-exposed parts. I was able to keep
> things separate enough that my C++ compilation units didn't include the
> Pg backend headers; they just exposed a pure C public interface. The Pg
> backend-using compilation units were written in C, and talked to the C++
> part over its exposed pure C interfaces.

Yeah, if you can design your code so that C++ never has to call back
into the core backend, that eliminates a large chunk of the pain.
Should we be documenting design ideas like this one?

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Marko Tiikkaja 2010-06-01 15:53:51 Re: Write-able CTEs, Update-able views, Hierarchical data, and optimistic locking
Previous Message Joshua Tolley 2010-06-01 13:28:57 Re: Statement Pooling