Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bUdwk-0008Ti-Of for pgsql-docs@arkaria.postgresql.org; Tue, 02 Aug 2016 17:57:42 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1bUdwk-0001td-BE for pgsql-docs@arkaria.postgresql.org; Tue, 02 Aug 2016 17:57:42 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1bUdwN-00015Y-Mp for pgsql-docs@postgresql.org; Tue, 02 Aug 2016 17:57:19 +0000 Received: from out5-smtp.messagingengine.com ([66.111.4.29]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1bUdwK-0005Tl-V0 for pgsql-docs@postgresql.org; Tue, 02 Aug 2016 17:57:18 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id 381892065B; Tue, 2 Aug 2016 13:57:16 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute2.internal (MEProxy); Tue, 02 Aug 2016 13:57:16 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=Sk5kp9bAYjGdHTM d8EdPq5719Dk=; b=O5Coe2WNM9j2gy6Vi9LG6pUm2Y83Q6CaSraafd3eHXQpiBb FFjxGTzC0xw/AbEFWcy0c7Ua50TEafL4SCnHAZVv4BLTRUNauGpDFcg8274moBLH 4eGMBO7DJOF5EDcr5Dfnhk0VhzsQmZ4Z8sEmnU1GGco1xDSy6A9X5e8+TYro= X-Sasl-enc: nn8f7K/5iWhOzEk5m2laHPAzRYcwbk7f8BVpJ+/YRRM4 1470160636 Received: from april.local (c-73-13-66-39.hsd1.pa.comcast.net [73.13.66.39]) by mail.messagingengine.com (Postfix) with ESMTPA id EDDFCCCDCC; Tue, 2 Aug 2016 13:57:15 -0400 (EDT) Subject: Re: max_worker_processes default not documented To: "David G. Johnston" References: <293b7a8d-9642-6e31-e425-360a6274eaf5@2ndquadrant.com> Cc: "pgsql-docs@postgresql.org" From: Peter Eisentraut Organization: 2ndQuadrant Message-ID: <8c24cd2a-9916-1bc6-896a-10ce37825862@2ndquadrant.com> Date: Tue, 2 Aug 2016 13:57:15 -0400 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -2.6 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-docs Precedence: bulk Sender: pgsql-docs-owner@postgresql.org 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 -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs