Bruce Momjian wrote: > Peter Geoghegan wrote: > > >> I would have > > >> imagined that ultimately, the call to the Pg C function must return, > > >> and therefore cannot affect stack unwinding within the C++ part of the > > >> program. > > > > > > That's the whole point; a longjmp breaks the call chain, and the > > > guarantee that eventually the stack will unwind as functions return. > > > > Yes, but my point was that if that occurs above the C++ code, it will > > never be affected by it. We have to longjmp() *over* C++ code before > > we have a problem. However, Bruce has answered the question of whether > > or not that happens - it does, so I guess it doesn't matter. > > Yes. I have updated the C++ doc patch to call it a "distant" > longjump().
Applied. -- Bruce Momjian <br...@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + None of us is going to be here forever. + -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
