Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bmOsh-0006A7-RS for pgsql-hackers@arkaria.postgresql.org; Tue, 20 Sep 2016 17:30:55 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1bmOsg-0002fP-W8 for pgsql-hackers@arkaria.postgresql.org; Tue, 20 Sep 2016 17:30:55 +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 1bmOse-0002et-PV for pgsql-hackers@postgresql.org; Tue, 20 Sep 2016 17:30:52 +0000 Received: from mail-wm0-x22a.google.com ([2a00:1450:400c:c09::22a]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1bmOsW-0003ye-Si for pgsql-hackers@postgresql.org; Tue, 20 Sep 2016 17:30:51 +0000 Received: by mail-wm0-x22a.google.com with SMTP id b130so47182597wmc.0 for ; Tue, 20 Sep 2016 10:30:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=Q9mel7tZm/i/AmyzFs2u7xIh1IuiuCm8WJe8yom4KFE=; b=z7lnP5bia7TrMzc329aRyBaLksBCeASMrhYuy6/eBSLnrLtcP44yQ6A9USWxK1HMyZ BAqbsk3Y5yu0xk893Kk3Y06i5x9T2OZbwMpTD3jL1F3FX/srEsTXc0AFLSpIu92sBzfS jF90PUVN0UrSHeGnLHDx/7IXekTPBk6ansH1d90PQ06Q6K/wNAitqxqiRcX3jKuvhlOX wH/pm6Ltprg+NHbDprGrmOOYmY/PT43HaLXoMJG1nHVJfCIDMzeO1DSuFF2MOpDQFsu9 tpA5Rp/Xm5cKqY2vSnjwaU0GyHBxJJIjS9GrfHT4W7J2EWqzVsR8Lam1Vb93PEQAgULo V6zw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=Q9mel7tZm/i/AmyzFs2u7xIh1IuiuCm8WJe8yom4KFE=; b=Bwnux3hJ7znYAnn37TaWVi+7ptbythk9UzAvhuHT/QqTRTIUluAANDD6sJKnDduXVh yUH4yKNBylQ31Qo+o3CB5JpmHrQ4x4joT3m6ycar5c6lDkMFfqqnuWzhuQ6Q20mIGq4Y o6L1yC+NikWOUNcKlab1mvLmPMGrreBiEPsrPE04Ry2MQpT54x4ubbSeFiyrnVEjfeHW AfvYasW+UPeRMuXTkSt0VnBkrBjCfGUqf6A0EYmHF4W/zPAOH/z4gh3YqxrUjJ7iLQw7 eSHPWHi2e+V+xDIJza68ayvqEWjaQTNsq+kEyMJqc6lnw3FvwixisAhXJbzoF1+gTcpB 1ohA== X-Gm-Message-State: AE9vXwPQ/GTPBtE9fja+qPrpITHQ//DEQXDjAIPjHAonzZrBGJtNHGs+B0lPf0KbC452IJMWFIzxwwbpLgP+l8svV1j4+jgCzldkj6qkdABXN+sdRDIdFwDp0kmzfd1rQV6/ncc3U4jIte+RN09w4FTxPoE/sVGCrP4qipjLPqGmT9qhLzPpdiP2ga0SBbjP5g== X-Received: by 10.28.102.6 with SMTP id a6mr4121930wmc.97.1474392642474; Tue, 20 Sep 2016 10:30:42 -0700 (PDT) Received: from [192.168.43.221] (ip-37-188-232-207.eurotel.cz. [37.188.232.207]) by smtp.gmail.com with ESMTPSA id b8sm5294409wmb.18.2016.09.20.10.30.39 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 20 Sep 2016 10:30:41 -0700 (PDT) Subject: Re: Rename max_parallel_degree? To: Robert Haas , Peter Eisentraut 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> 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: Petr Jelinek Message-ID: <2471b149-4f5f-77fd-bc8c-70e8d1cecf5c@2ndquadrant.com> Date: Tue, 20 Sep 2016 19:30:38 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 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 20/09/16 17:47, Robert Haas wrote: > On Tue, Sep 20, 2016 at 11:27 AM, Peter Eisentraut > wrote: >> On 9/19/16 2:18 PM, Robert Haas wrote: >>> I suggest that we make it part of bgw_flags, but use a bitmask for it, >>> like this: >>> >>> #define BGWORKER_CLASS_MASK 0x00f0 >>> #define BGWORKER_CLASS_PARALLEL 0x0010 >>> /* add additional bgworker classes here */ >> >> Unless we have a mechanism that makes use of this somehow, this attempt >> at categorizing might be premature. > > My main reason for wanting is that I suspect there will be a similar > desire to limit the number of replication workers at some point. > Yes there definitely is desire to use this for replication workers as well. The logical replication launcher currently handles the limit by itself but I'd definitely prefer to reuse something more generic. -- Petr Jelinek http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, 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