Re: bg worker: general purpose requirements - Mailing list pgsql-hackers

From Markus Wanner
Subject Re: bg worker: general purpose requirements
Date
Msg-id 4C98F9C8.8020105@bluegap.ch
Whole thread Raw
In response to Re: bg worker: general purpose requirements  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On 09/21/2010 05:59 PM, Robert Haas wrote:
> Oh, wow.  Is there another limit on the total number of bgworkers?

There currently are three GUCs that control bgworkers:

max_background_workers
min_spare_background_workers
max_spare_background_workers

The first replaces the former autovacuum_max_workers GUC. As before, it
is an overall limit, much like max_connections.

The later two are additional. They are per-database lower and upper
limits for the amount of idle workers an any point in time. These later
two are what I'm referring to as the min/max approach. And what I'm
arguing cannot be replaced by a timeout without loosing functionality.

Regards

Markus Wanner


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: .gitignore files, take two
Next
From: Andrew Dunstan
Date:
Subject: Re: Git conversion status