| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Chapman Flack <chap(at)anastigmatix(dot)net> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: who calls InitializeTimeouts() ? |
| Date: | 2016-11-03 14:01:44 |
| Message-ID: | CA+TgmoY-iaqGYm=FA9yMgZ_7t7E8KkeU8dAWCevfUn-mj7zKCA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Nov 2, 2016 at 11:10 PM, Chapman Flack <chap(at)anastigmatix(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2016-11-03 14:07:31 | Re: plan_rows confusion with parallel queries |
| Previous Message | Guillaume Lelarge | 2016-11-03 14:01:18 | Re: Exclude pg_largeobject form pg_dump |