On 2015-08-14 11:10:14 -0700, Peter Geoghegan wrote:
> On Fri, Aug 14, 2015 at 10:28 AM, Tom Lane <t...@sss.pgh.pa.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
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
