Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bnQ1j-0001Vq-IA for pgsql-hackers@arkaria.postgresql.org; Fri, 23 Sep 2016 12:56:27 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1bnQ1j-0008BA-4x for pgsql-hackers@arkaria.postgresql.org; Fri, 23 Sep 2016 12:56:27 +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 1bnQ0K-0006WV-M9 for pgsql-hackers@postgresql.org; Fri, 23 Sep 2016 12:55:00 +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 1bnQ0I-0006bN-5f for pgsql-hackers@postgresql.org; Fri, 23 Sep 2016 12:54:59 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id 8B7F1205CF; Fri, 23 Sep 2016 08:54:56 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute2.internal (MEProxy); Fri, 23 Sep 2016 08:54:56 -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=CXgMNfZZG37V75f xM+9a9I+KFMA=; b=nEes5wnlYdP4t9Y2qUs621pWVVGspVdkK2r8XD8YlTzMBD0 qXHhNB/C0WmLhGUWMKWU2tl+UHcm7svHX78Dbp7fcdQlxIHV8Acy1+L7XKBaydHm o2lbdAME9btOQ/90Pkx7XZOVH5HZGDn1h9KtBUS/sRTMlpRruRnIvMDjKWOk= X-Sasl-enc: e/JTWklro7+qc7ShUbFy1il4UuhVoOdw+1sw0QpH2kMD 1474635296 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 E736FCCE9E; Fri, 23 Sep 2016 08:54:55 -0400 (EDT) Subject: Re: Rename max_parallel_degree? To: Robert Haas References: <20160426152217.GA548975@alvherre.pgsql> <9f84548d-8b59-b5c8-510d-991f8ee3ab20@dalibo.com> <20312f33-c14e-0d3f-a79f-95212f64a38c@dalibo.com> <9a3ca4ad-c3ea-2c02-499a-029e053fedda@dalibo.com> <7ef3a740-8c64-764d-9f02-b27132d89602@2ndquadrant.com> Cc: Julien Rouhaud , Amit Kapila , Tom Lane , Josh Berkus , "David G. Johnston" , Peter Geoghegan , Noah Misch , David Rowley , Alvaro Herrera , Magnus Hagander , Bruce Momjian , PostgreSQL-development From: Peter Eisentraut Organization: 2ndQuadrant Message-ID: Date: Fri, 23 Sep 2016 08:54:55 -0400 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 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 9/20/16 4:07 PM, Robert Haas wrote: > No, I'm assuming that the classes would be built-in. A string tag > seems like over-engineering to me, particularly because the postmaster > needs to switch on the tag, and we need to be very careful about the > degree to which the postmaster trusts the contents of shared memory. I'm hoping that we can come up with something that extensions can participate in, without the core having to know ahead of time what those extensions are or how they would be categorized. My vision is something like max_processes = 512 # requires restart process_allowances = 'connection:300 superuser:10 autovacuum:10 parallel:30 replication:10 someextension:20 someotherextension:20' # does not require restart -- 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