Postgres Pro
Downloads
Home   >   mailing lists

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

From Robert Haas
Subject Re: Making BackgroundWorkerHandle a complete type or offering a worker enumeration API?
Date
Msg-id CA+TgmoaM8O6wY3LUiQXjTbyPHiCoVO9u3e1A+5HwSQrh98b6xw@mail.gmail.com
Whole thread Raw
In response to Re: Making BackgroundWorkerHandle a complete type or offering a worker enumeration API?  (Craig Ringer <craig@2ndquadrant.com>)
Responses Re: Making BackgroundWorkerHandle a complete type or offering a worker enumeration API?  (Craig Ringer <craig@2ndquadrant.com>)
List pgsql-hackers
Tree view 
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.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Something is broken in logical decoding with CLOBBER_CACHE_ALWAYS
Next
From: Craig Ringer
Date:
Subject: Re: Making BackgroundWorkerHandle a complete type or offering a worker enumeration API?