On Wed, Nov 2, 2016 at 11:10 PM, Chapman Flack <c...@anastigmatix.net> wrote: > It looks like for about 3 years, PL/Java has been calling > InitializeTimeouts before calling RegisterTimeout. Looking over > the callers of InitializeTimeouts in core, though, it appears > that an extension like PL/Java should be able to assume it has > already been called, and in fact would be rude to call it again, > as it isn't idempotent and could conceivably clobber somebody > else's timeouts.
Yep. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
