Re: bg worker: patch 1 of 6 - permanent process

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: bg worker: patch 1 of 6 - permanent process
Дата
Msg-id 9243.1284486940@sss.pgh.pa.us
обсуждение исходный текст
Ответ на bg worker: patch 1 of 6 - permanent process  (Markus Wanner <markus@bluegap.ch>)
Ответы Re: bg worker: patch 1 of 6 - permanent process  (Markus Wanner <markus@bluegap.ch>)
Список pgsql-hackers
Markus Wanner <markus@bluegap.ch> writes:
> On 09/14/2010 07:46 PM, Tom Lane wrote:
>> That seems like a fairly large can of worms to open: we have never tried
>> to make backends switch from one database to another, and I don't think
>> I'd want to start such a project with autovac.

> They don't. Even with bgworker, every backend stays connected to the 
> same backend. You configure the min and max amounts of idle backends 
> *per database*. Plus the overall max of background workers, IIRC.

So there is a minimum of one avworker per database?  That's a guaranteed
nonstarter.  There are many people with thousands of databases, but no
need for thousands of avworkers.

I'm also pretty unclear why you speak of min and max numbers of workers
when the proposal (AIUI) is to have the workers there always, rather
than have them come and go.
        regards, tom lane


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Alvaro Herrera
Дата:
Сообщение: Re: bg worker: patch 1 of 6 - permanent process
Следующее
От: Markus Wanner
Дата:
Сообщение: Re: bg worker: patch 1 of 6 - permanent process