Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1b7rhZ-0007w7-1V for pgsql-hackers@arkaria.postgresql.org; Tue, 31 May 2016 21:59:53 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1b7rhY-0002H5-Gt for pgsql-hackers@arkaria.postgresql.org; Tue, 31 May 2016 21:59: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 1b7rgC-0000gz-Su for pgsql-hackers@postgresql.org; Tue, 31 May 2016 21:58:28 +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 1b7rg9-0002WK-Q8 for pgsql-hackers@postgresql.org; Tue, 31 May 2016 21:58:28 +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 u4VLwE8r005642; Tue, 31 May 2016 17:58:14 -0400 From: Tom Lane To: Alvaro Herrera cc: Robert Haas , Josh berkus , Peter Eisentraut , Peter Geoghegan , Noah Misch , David Rowley , Amit Kapila , Magnus Hagander , Bruce Momjian , PostgreSQL-development Subject: Re: Rename max_parallel_degree? In-reply-to: <20160531202742.GA896974@alvherre.pgsql> References: <20160531202742.GA896974@alvherre.pgsql> Comments: In-reply-to Alvaro Herrera message dated "Tue, 31 May 2016 16:27:42 -0400" Date: Tue, 31 May 2016 17:58:14 -0400 Message-ID: <5641.1464731894@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 Alvaro Herrera writes: > Robert Haas wrote: >> I just want to point out that if we change #1, we're breaking >> postgresql.conf compatibility for, IMHO, not a whole lot of benefit. >> I'd just leave it alone. > We can add the old name as a synonym in guc.c to maintain compatibility. I doubt this is much of an issue at this point; max_worker_processes has only been there a release or so, and surely there are very few people explicitly setting it, given its limited use-case up to now. It will be really hard to change it after 9.6, but I think we could still get away with that today. 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