Re: max_worker_processes default not documented

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
Cc: "pgsql-docs(at)postgresql(dot)org" <pgsql-docs(at)postgresql(dot)org>
Subject: Re: max_worker_processes default not documented
Date: 2016-08-02 17:57:15
Message-ID: 8c24cd2a-9916-1bc6-896a-10ce37825862@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

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

In response to

Browse pgsql-docs by date

  From Date Subject
Next Message Peter Eisentraut 2016-08-02 23:25:51 Re: Need clarification on "another server might be running; trying to start server anyway"
Previous Message Tom Lane 2016-08-02 17:34:01 Re: NOTIFY man page still recommends rules