Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1b8psC-0006vO-Od for pgsql-hackers@arkaria.postgresql.org; Fri, 03 Jun 2016 14:14:52 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1b8psC-0003Kd-8H for pgsql-hackers@arkaria.postgresql.org; Fri, 03 Jun 2016 14:14:52 +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 1b8psA-0003J7-FV for pgsql-hackers@postgresql.org; Fri, 03 Jun 2016 14:14:50 +0000 Received: from zmcc-5-mx.zmailcloud.com ([192.198.93.228]) by magus.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1b8ps7-0006St-2F for pgsql-hackers@postgresql.org; Fri, 03 Jun 2016 14:14:49 +0000 Received: from zmcc-5-mta-1.zmailcloud.com (127.37.197.104.bc.googleusercontent.com [104.197.37.127]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by zmcc-5-mx.zmailcloud.com (Postfix) with ESMTPS id 564B3520268; Fri, 3 Jun 2016 10:14:45 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by zmcc-5-mta-1.zmailcloud.com (Postfix) with ESMTP id F1185C1FA0; Fri, 3 Jun 2016 14:14:44 +0000 (UTC) Received: from zmcc-5-mta-1.zmailcloud.com ([127.0.0.1]) by localhost (zmcc-5-mta-1.zmailcloud.com [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id RQyzdcT6N13R; Fri, 3 Jun 2016 14:14:44 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by zmcc-5-mta-1.zmailcloud.com (Postfix) with ESMTP id 618C7C2E88; Fri, 3 Jun 2016 14:14:44 +0000 (UTC) X-Virus-Scanned: amavisd-new at zmcc-5-mta-1.zmailcloud.com Received: from zmcc-5-mta-1.zmailcloud.com ([127.0.0.1]) by localhost (zmcc-5-mta-1.zmailcloud.com [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id XKaPRMEEFTxW; Fri, 3 Jun 2016 14:14:44 +0000 (UTC) Received: from redhat.com (c-98-246-109-153.hsd1.or.comcast.net [98.246.109.153]) by zmcc-5-mta-1.zmailcloud.com (Postfix) with ESMTPSA id 4784DC1FA0; Fri, 3 Jun 2016 14:14:43 +0000 (UTC) Subject: Re: Rename max_parallel_degree? To: Peter Eisentraut , 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 , Peter Geoghegan , Noah Misch , David Rowley , Amit Kapila , Magnus Hagander , Bruce Momjian , PostgreSQL-development From: Josh berkus Message-ID: <575190D2.5050107@agliodbs.com> Date: Fri, 3 Jun 2016 07:14:42 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Pg-Spam-Score: -1.9 (-) 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 06/02/2016 09:33 PM, Peter Eisentraut wrote: > 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. >>> >>> >>> =E2=80=8BGiven 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. >=20 > 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. Now that's crazy talk. I mean, next thing you'll be saying that we need the ability to monitor this, or even change it at runtime. Where does the madness end? ;-) Seriously, you have a point here; it's maybe time to stop tackling process management per server piecemeal. Question is, who wants to work on this? --=20 -- Josh Berkus Red Hat OSAS (any opinions are my own) --=20 Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers