| From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Making BackgroundWorkerHandle a complete type or offering a worker enumeration API? |
| Date: | 2014-12-15 16:34:49 |
| Message-ID: | 548F0DA9.7090903@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 12/16/2014 12:31 AM, Robert Haas wrote:
> On Mon, Dec 15, 2014 at 11:28 AM, Craig Ringer <craig(at)2ndquadrant(dot)com> wrote:
>>> >> If that's not good for some reason, my second choice is adding a
>>> >> BGWORKER_UNREGISTER_AFTER_CRASH flag. That seems much simpler and
>>> >> less cumbersome than your other proposal.
>> >
>> > That'd be my preference.
> OK, let's do that, then.
Right-o.
I had an earlier patch that added unregistration on exit(0) and also
added a flag like this. Only the first part got committed. I'll
resurrect it and rebase it on top of master.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alex Shulgin | 2014-12-15 16:38:16 | Re: [PATCH] HINT: pg_hba.conf changed since last config reload |
| Previous Message | Robert Haas | 2014-12-15 16:31:20 | Re: Making BackgroundWorkerHandle a complete type or offering a worker enumeration API? |