Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1b8pKS-0004Vp-0E for pgsql-hackers@arkaria.postgresql.org; Fri, 03 Jun 2016 13:40:00 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1b8pKR-0006Ib-6E for pgsql-hackers@arkaria.postgresql.org; Fri, 03 Jun 2016 13:39:59 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1b8pKQ-0006IV-R6 for pgsql-hackers@postgresql.org; Fri, 03 Jun 2016 13:39:58 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1b8pKN-0005Gt-Qo for pgsql-hackers@postgresql.org; Fri, 03 Jun 2016 13:39:58 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id u53DdhET011331; Fri, 3 Jun 2016 09:39:43 -0400 From: Tom Lane To: Robert Haas cc: "David G. Johnston" , Josh berkus , Amit Kapila , Peter Geoghegan , Noah Misch , David Rowley , Alvaro Herrera , Magnus Hagander , Bruce Momjian , PostgreSQL-development Subject: Re: Rename max_parallel_degree? In-reply-to: References: <20160426152217.GA548975@alvherre.pgsql> <574DC881.5010006@agliodbs.com> <17944.1464790245@sss.pgh.pa.us> <7570.1464816591@sss.pgh.pa.us> <575051AF.2090101@agliodbs.com> <21660.1464882811@sss.pgh.pa.us> <57508E69.9000505@agliodbs.com> <57509894.9080507@agliodbs.com> Comments: In-reply-to Robert Haas message dated "Fri, 03 Jun 2016 08:34:47 -0400" Date: Fri, 03 Jun 2016 09:39:43 -0400 Message-ID: <11330.1464961183@sss.pgh.pa.us> X-Pg-Spam-Score: -3.3 (---) 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 Robert Haas writes: > I think we should just go with max_parallel_workers for a limit on > total parallel workers within max_work_processes, and > max_parallel_workers_per_gather for a per-Gather limit. It's slightly > annoying that we may end up renaming the latter GUC, but not as > annoying as spending another three weeks debating this and missing > beta2. +1. I'm not as convinced as you are that we'll replace the GUC later, but in any case this is an accurate description of the current semantics. And I'm really *not* in favor of fudging the name with the intent of changing the GUC's semantics later --- that would fail all sorts of compatibility expectations. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers