| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Peter Geoghegan <pg(at)heroku(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, jacques klein <jacques(dot)klei(at)googlemail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: How to compile, link and use a C++ extension |
| Date: | 2015-08-14 18:16:47 |
| Message-ID: | 20150814181647.GM4955@awork2.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2015-08-14 11:10:14 -0700, Peter Geoghegan wrote:
> On Fri, Aug 14, 2015 at 10:28 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> > Yeah. The painful issues you're going to face are not that. They are
> > memory management (C++ "new" does not talk to palloc or vice versa)
> > and error handling ("throw" does not interoperate with PG_TRY()).
>
> It's worse than that. Any use of longjmp() will cause undefined
> behavior in C++. That's because each C++ object's destructor will not
> be called (possibly other reasons, too).
Only if that longjmp goes through C++ code with non-POD objects. Which
you should pretty much never allow.
- Andres
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bear Giles | 2015-08-14 18:18:04 | FDW question - how to identify columns to populate in response? |
| Previous Message | Peter Geoghegan | 2015-08-14 18:10:14 | Re: How to compile, link and use a C++ extension |