Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1b8gnH-0002mK-1m for pgsql-hackers@arkaria.postgresql.org; Fri, 03 Jun 2016 04:33: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 1b8gnG-0001SA-8O for pgsql-hackers@arkaria.postgresql.org; Fri, 03 Jun 2016 04:33:10 +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 1b8gnE-0001Ph-Vw for pgsql-hackers@postgresql.org; Fri, 03 Jun 2016 04:33:09 +0000 Received: from out2-smtp.messagingengine.com ([66.111.4.26]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1b8gnB-0003kJ-Bf for pgsql-hackers@postgresql.org; Fri, 03 Jun 2016 04:33:08 +0000 Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id CEF0720907; Fri, 3 Jun 2016 00:33:03 -0400 (EDT) Received: from frontend1 ([10.202.2.160]) by compute7.internal (MEProxy); Fri, 03 Jun 2016 00:33:03 -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=cb33a97tJ5ThO1r 3zxKj/nTnWmE=; b=AbkhxyPiPRoTXTPTjWiXJWcoHHbBi1fog6NI2GmPwxXYQDl H8qcfJ93XbTe5ZJRG50vOqeuhcXxuPZ+S1IfhL8XSfTuz84/l4itcic6o0poPdjJ P8WzeFCdQyOGal0iDmlyPG4WP5MGgEH+HbSJ/mOCIsEjMTHTS8Wux1kJM5OE= X-Sasl-enc: 9Foxa7odFbN2jqg24UIbM8868SPQIuGbIjUyeAwweEX+ 1464928383 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 4076EF29F5; Fri, 3 Jun 2016 00:33:03 -0400 (EDT) Subject: Re: Rename max_parallel_degree? To: Petr Jelinek , "David G. Johnston" References: <20160531202742.GA896974@alvherre.pgsql> <5641.1464731894@sss.pgh.pa.us> <574F030F.7030108@2ndquadrant.com> <575105B4.60506@2ndquadrant.com> Cc: Jim Nasby , Robert Haas , Tom Lane , Alvaro Herrera , Josh berkus , Peter Geoghegan , Noah Misch , David Rowley , Amit Kapila , Magnus Hagander , Bruce Momjian , PostgreSQL-development From: Peter Eisentraut Organization: 2ndQuadrant Message-ID: Date: Fri, 3 Jun 2016 00:33:02 -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: <575105B4.60506@2ndquadrant.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit 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 6/3/16 12:21 AM, Petr Jelinek wrote: > On 01/06/16 17:55, David G. Johnston wrote: >> On Wed, Jun 1, 2016 at 11:45 AM, Petr Jelinek > >wrote: >> >> That GUC also controls worker processes that are started by >> extensions, not just ones that parallel query starts. This is btw >> one thing I don't like at all about how the current limits work, the >> parallel query will fight for workers with extensions because they >> share the same limit. >> >> >> ​Given that this models reality the GUC is doing its job. Now, maybe we >> need additional knobs to give the end-user the ability to influence how >> those fights will turn out. > > Agreed, my point is that I think we do need additional knob. We need one knob to control how many process slots to create at server start, and then a bunch of sliders to control how to allocate those between regular connections, superuser connections, replication, autovacuum, parallel workers, background workers (by tag/label/group), and so on. -- 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