Thread: max_worker_processes default not documented
While this may be in the postgresql.conf it's absence in the docs is made noticeable by the fact both the immediately preceding and subsequent items in the 9.6 docs specify their default values. Furthermore, max_parallel_degree defaults to 2 but the workers come from the pool sized using max_worker_processes - provoking the very question as to how many is 2 relative to the default pool size.
David J.
On 5/7/16 11:16 PM, David G. Johnston wrote: > While this may be in the postgresql.conf it's absence in the docs is made > noticeable by the fact both the immediately preceding and subsequent items > in the 9.6 docs specify their default values. Furthermore, > max_parallel_degree defaults to 2 but the workers come from the pool sized > using max_worker_processes - provoking the very question as to how many is > 2 relative to the default pool size. done -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
On Thursday, May 12, 2016, Peter Eisentraut <peter.eisentraut@2ndquadrant.com> wrote:
On 5/7/16 11:16 PM, David G. Johnston wrote:While this may be in the postgresql.conf it's absence in the docs is made
noticeable by the fact both the immediately preceding and subsequent items
in the 9.6 docs specify their default values. Furthermore,
max_parallel_degree defaults to 2 but the workers come from the pool sized
using max_worker_processes - provoking the very question as to how many is
2 relative to the default pool size.
done
Thanks. Now for a related question. Are any of those workers permanently in use? And what processes use them. I can think of checkpoint writer and autovacuum off the top of my head that are potential candidates.
David J.
On 5/12/16 9:24 AM, David G. Johnston wrote: > Thanks. Now for a related question. Are any of those workers > permanently in use? And what processes use them. I can think of > checkpoint writer and autovacuum off the top of my head that are > potential candidates. max_worker_processes only controls "background workers". The other facilities you mention don't count as such (confusingly perhaps). Before 9.6, the only background workers were from extensions. In 9.6, the parallel workers also use the background worker facilities and count against max_worker_processes. More documentation is possible here. I think maybe a section somewhere that summarizes all the parallel-related settings. And also something in the release notes noting that max_worker_processes is now also used by built-in facilities, so you should increase it if you have previously adjusted it for something. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services