Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1b7uPH-0004Ot-EG for pgsql-hackers@arkaria.postgresql.org; Wed, 01 Jun 2016 00:53:11 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1b7uPG-0006Ez-H1 for pgsql-hackers@arkaria.postgresql.org; Wed, 01 Jun 2016 00:53:10 +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 1b7uNv-0004ex-EL for pgsql-hackers@postgresql.org; Wed, 01 Jun 2016 00:51:47 +0000 Received: from out2-smtp.messagingengine.com ([66.111.4.26]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1b7uNs-0001Fr-Fq for pgsql-hackers@postgresql.org; Wed, 01 Jun 2016 00:51:46 +0000 Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 52FFD2085C; Tue, 31 May 2016 20:51:43 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute6.internal (MEProxy); Tue, 31 May 2016 20:51:43 -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=RLC6rFd6GtVYp6o 3kZUmkjX0RsA=; b=BtdrIar1axyKRaMle9/ktzYCBOVWWuEj6RQZugcJ+CewnkJ wW8o8QBi6Eel6Ay/YQWIqvm6WZUpvm7yvk3FzERpTpVRJvaDzyAAYdeDfiH0pPv3 /Bs/zFfseGzidpICvtxXOrG1sKxjKv10NxrUp9i3OruArlXIXRNzbUY7pNVA= X-Sasl-enc: VMotMWjN7879rso4eowJtIIKS9BmpouwgZtDf4xxAkZf 1464742303 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 BC62CCCD99; Tue, 31 May 2016 20:51:42 -0400 (EDT) Subject: Re: Rename max_parallel_degree? To: Tom Lane , Alvaro Herrera References: <20160531195553.GA895326@alvherre.pgsql> <31423.1464725081@sss.pgh.pa.us> Cc: Robert Haas , Josh berkus , Peter Geoghegan , Noah Misch , David Rowley , Amit Kapila , Magnus Hagander , Bruce Momjian , PostgreSQL-development From: Peter Eisentraut Organization: 2ndQuadrant Message-ID: Date: Tue, 31 May 2016 20:51:42 -0400 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.1.0 MIME-Version: 1.0 In-Reply-To: <31423.1464725081@sss.pgh.pa.us> Content-Type: text/plain; charset=windows-1252; format=flowed 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-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org On 5/31/16 4:04 PM, Tom Lane wrote: > The name should be closely related to what we use for #3. I could go for > max_total_parallel_workers for #2 and max_parallel_workers for #3. > Or maybe max_parallel_workers_total? Most cluster-wide settings like this are named max_something (max_connections, max_wal_senders, max_replication_slots), whereas things that apply on a lower level are named max_something_per_something (max_files_per_process, max_locks_per_transations). So let's leave max_worker_processes mostly alone and not add any _total_, _absolute_, _altogether_. ;-) -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers