Re: Making BackgroundWorkerHandle a complete type or offering a worker enumeration API? - Mailing list pgsql-hackers

From Craig Ringer
Subject Re: Making BackgroundWorkerHandle a complete type or offering a worker enumeration API?
Date
Msg-id 548F0DA9.7090903@2ndquadrant.com
Whole thread Raw
In response to Re: Making BackgroundWorkerHandle a complete type or offering a worker enumeration API?  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On 12/16/2014 12:31 AM, Robert Haas wrote:
> On Mon, Dec 15, 2014 at 11:28 AM, Craig Ringer <craig@2ndquadrant.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



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Making BackgroundWorkerHandle a complete type or offering a worker enumeration API?
Next
From: Alex Shulgin
Date:
Subject: Re: [PATCH] HINT: pg_hba.conf changed since last config reload