Received: from malur.postgresql.org ([2a02:16a8:dc51::56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fWIIA-0000XN-Ci for pgsql-hackers@arkaria.postgresql.org; Fri, 22 Jun 2018 09:23:42 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fWII8-0007zc-Id for pgsql-hackers@arkaria.postgresql.org; Fri, 22 Jun 2018 09:23:40 +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.89) (envelope-from ) id 1fWII8-0007zV-5i for pgsql-hackers@lists.postgresql.org; Fri, 22 Jun 2018 09:23:40 +0000 Received: from mail-oi0-x242.google.com ([2607:f8b0:4003:c06::242]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1fWII5-0000yI-Hs for pgsql-hackers@lists.postgresql.org; Fri, 22 Jun 2018 09:23:38 +0000 Received: by mail-oi0-x242.google.com with SMTP id e8-v6so5568303oii.2 for ; Fri, 22 Jun 2018 02:23:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=ANa5w5e4XiWX/R4PFo1na+4gJjEpKF2HS4KgyzANvI0=; b=cumyWgk6ASK5JsUyWKBPCmN0XPe+rfSiqt3rA9uWmbthObNlGHVV2Z3fYY4n+0MMl6 yXZ20Is5yV7TsfdXwl+R3N/a/E8q61sCQJx8OMeqWrdElVxhLQGQCdcMMIdHb93TlOkC jLk9tXxUoHW7o6zmKMiK7JNIEUCjh2bLhR+uZcFYdWP8DQ/Zh+ov/rfNJ8U09nbwJz2/ YAXv5kwGQBpnR/BJoaFClz7VkMEfSSIPJEYInOfcJX3Pq7zT2GhxRf+5HtTorIlnf2yx NYmoQYtnioAGRQLpXAtnhO5nsgcmn3IfWZIzqZPxlC29tRnhVMW3HYQdYh2PADSDQTrv 3Cwg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=ANa5w5e4XiWX/R4PFo1na+4gJjEpKF2HS4KgyzANvI0=; b=MTWDF3I0N2uDKLxUX81zBq1SUisPc9V002R67sMuSIXRBTqWcxAulcAD9TPqoFWN3j SB8mr7btJ6Y/haj8b++EMSmMqWTvlg2k9O54Xw1qsrfhrFGiMKCaxD8Fk6N1SXg6oU7X 2ZA6Nwjqmpn8xx2aW+204S06DmqKTtzqSgkTMJgOqY+JmnsdMAox6TM8Bm6xH90cU7Ti 22lv2e+94QQpZGFuH6DtXhBzaQsxWSnH9RdP3yvLw5clcm9hrsmgBqW7K5zHGU6Undsl EdcpMVZtMmckSxgUMxbAgrni+R4XqjT57+GwK3mFNFbJO+VvbZPLQCcMfbmBpbT1/An7 UoIw== X-Gm-Message-State: APt69E26bNWi4JRn4oW2gpg1DkBkl6RInitFE6x+IxSH5JuuxJO9JagJ APpvzsFKnZNn5PJXnBCx+N4so3HD+1LbNjCu+RE= X-Google-Smtp-Source: ADUXVKI57K6uGPcIRfbS0oakfVt750lWUujoI4t1O7+v2JNu3G6Zx6zducaX/CojNMR4yl2etVpofzXqk0WTFg8nc9k= X-Received: by 2002:aca:d0d6:: with SMTP id j83-v6mr361054oiy.189.1529659416469; Fri, 22 Jun 2018 02:23:36 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:ac9:3c08:0:0:0:0:0 with HTTP; Fri, 22 Jun 2018 02:23:36 -0700 (PDT) In-Reply-To: <20180620151349.GB7500@momjian.us> References: <20171026194515.GV21735@telsasoft.com> <20180128235310.GA5024@momjian.us> <20180525010025.GT30060@telsasoft.com> <20180620151349.GB7500@momjian.us> From: Amit Kapila Date: Fri, 22 Jun 2018 14:53:36 +0530 Message-ID: Subject: Re: add default parallel query to v10 release notes? (Re: [PERFORM] performance drop after upgrade (9.6 > 10)) To: Bruce Momjian Cc: Justin Pryzby , PostgreSQL Hackers Content-Type: text/plain; charset="UTF-8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Wed, Jun 20, 2018 at 8:43 PM, Bruce Momjian wrote: > On Thu, May 24, 2018 at 08:00:25PM -0500, Justin Pryzby wrote: > > So I did some research on this, particularly to find out how it was > missed in the PG 10 release notes. It turns out that > max_parallel_workers_per_gather has always defaulted to 2 in head, and > this was changed to default to 0 in the 9.6 branch: > > commit f85b1a84152f7bf019fd7a2c5eede97867dcddbb > Author: Robert Haas > Date: Tue Aug 16 08:09:15 2016 -0400 > > Disable parallel query by default. > > Per discussion, set the default value of max_parallel_workers_per_gather > to 0 in 9.6 only. We'll leave it enabled in master so that it gets > more testing and in the hope that it can be enable by default in v10. > > Therefore, there was no commit to find in the PG 10 commit logs. :-O > Not sure how we can avoid this kind of problem in the future. > > The attached patch adds a PG 10.0 release note item about this change. > Your proposed text looks good to me. -- With Regards, Amit Kapila. EnterpriseDB: http://www.enterprisedb.com