Re: Making BackgroundWorkerHandle a complete type or offering a worker enumeration API?

Поиск
Список
Период
Сортировка
От Robert Haas
Тема Re: Making BackgroundWorkerHandle a complete type or offering a worker enumeration API?
Дата
Msg-id CA+TgmoaM8O6wY3LUiQXjTbyPHiCoVO9u3e1A+5HwSQrh98b6xw@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Making BackgroundWorkerHandle a complete type or offering a worker enumeration API?  (Craig Ringer <craig@2ndquadrant.com>)
Ответы Re: Making BackgroundWorkerHandle a complete type or offering a worker enumeration API?  (Craig Ringer <craig@2ndquadrant.com>)
Список pgsql-hackers
Дерево обсуждения 
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 по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: Something is broken in logical decoding with CLOBBER_CACHE_ALWAYS
Следующее
От: Craig Ringer
Дата:
Сообщение: Re: Making BackgroundWorkerHandle a complete type or offering a worker enumeration API?