Andres Freund <andres@anarazel.de> writes:
> Perhaps, for v11, we should actually make sure there's no memory context
> etc set during _PG_init() to catch such problems earlier?
I don't see much of a way to do that in the "typical" case where
the library load happens as a result of a SQL command. You can't
just say "oh, we're not in a transaction" and then later "wait,
yes we are".
Maybe we should recommend that extension authors test their libraries
in the preload scenario ...
regards, tom lane
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs