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 1fM15z-0007B9-1r for pgsql-hackers@arkaria.postgresql.org; Fri, 25 May 2018 01:00:39 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fM15t-00084s-RT for pgsql-hackers@arkaria.postgresql.org; Fri, 25 May 2018 01:00:33 +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.89) (envelope-from ) id 1fM15t-00084j-EQ for pgsql-hackers@lists.postgresql.org; Fri, 25 May 2018 01:00:33 +0000 Received: from mail-io0-x231.google.com ([2607:f8b0:4001:c06::231]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1fM15p-0005pd-HA for pgsql-hackers@lists.postgresql.org; Fri, 25 May 2018 01:00:32 +0000 Received: by mail-io0-x231.google.com with SMTP id a10-v6so4528503ioc.9 for ; Thu, 24 May 2018 18:00:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telsasoft-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=tg/pzhSLv5kl4MIUlVmmqQhGMuyC9rZawGEs0iMvqnI=; b=bTDFUtupfLhDEnSLaAraky1OXoSOwmUuwgGwq8IK+NH1EJSBmRKZ+hnWZRUZDEd5o1 HfcmrFk1mVEoKnIKN6eQLwogTyQgc2Ew1TK9rRAROj0DT5wT4lN2+stmMm5Z0iW7DJxU 70dJ7+XMzjb38q2pRJhVR5hwn+J9ZTYi4YRySQM6Bve/raTz5NTlyAZ6V1PmRC4sQs7l GbvXwpRyik7UOdnXzSjWb5j4GjqvRgjW5IxhapvoXUvjzGdF3HZo45K7BDT9sb/FqDWe +/cXadMj2jLjvmeluT41ItEL+/DzTO0A4RRV33XIlW8tklTv1cH/c5QcJ5rbTrbBKBBd weVA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=tg/pzhSLv5kl4MIUlVmmqQhGMuyC9rZawGEs0iMvqnI=; b=S5RVOIgiCuwBlnO+hcjlJJT7TH1Fsbt8nyulJVbpUqov8LPI8i+ivH4OgDwatgYjpe B0J/Q9Lx/Ln+WErn9u9zQ42obcStJ/o/raQg0b5WJhe9rblUbjb5hHZdr0Bd4vdg9Z2p Q8/LM/7KM6Jr+kIjYmzP9kvkjYOGWvuj/K5yljwz6Ba3PepKmUmv33rWRuEuP0sxQEGK 64+hCoIj9bskN2T5FOF4n11r7L7fQ58/pXRGlZVuW2d9Vumwzd8UfsqccIqCx6EZBVdk iJwfBzV1aqX/6ntpSGbnc/yD9gdcFLgodkrllVx9OPA2EyXRF6/dEgPqaNLyoPy8NkTP 3m5A== X-Gm-Message-State: ALKqPwcjvPS2rugBTrmmrgdc0lqWjOzzb3O4qhT52sf3Aw81cYOaw9r9 BRaA10GXx5CCNJTzMgZfot0lUV4UV60= X-Google-Smtp-Source: ADUXVKKU9oln0rl6QrLuIod+TRqRZaHPfFgpx440HsRdQXSx8YzkSolgfxSNNrbStQNWg9ABr1X7eQ== X-Received: by 2002:a6b:6e11:: with SMTP id d17-v6mr225109ioh.159.1527210026892; Thu, 24 May 2018 18:00:26 -0700 (PDT) Received: from pryzbyj (charmander.telsasoft.com. [50.244.222.1]) by smtp.gmail.com with ESMTPSA id o137-v6sm12661399ioe.3.2018.05.24.18.00.26 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 24 May 2018 18:00:26 -0700 (PDT) Received: by pryzbyj (Postfix, from userid 1000) id 770138019C8; Thu, 24 May 2018 20:00:25 -0500 (CDT) Date: Thu, 24 May 2018 20:00:25 -0500 From: Justin Pryzby To: Bruce Momjian Cc: pgsql-hackers@lists.postgresql.org Subject: add default parallel query to v10 release notes? (Re: [PERFORM] performance drop after upgrade (9.6 > 10)) Message-ID: <20180525010025.GT30060@telsasoft.com> References: <20171026194515.GV21735@telsasoft.com> <20180128235310.GA5024@momjian.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180128235310.GA5024@momjian.us> User-Agent: Mutt/1.5.23 (2014-03-12) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Moving to -hackers; On Sun, Jan 28, 2018 at 06:53:10PM -0500, Bruce Momjian wrote: > On Thu, Oct 26, 2017 at 02:45:15PM -0500, Justin Pryzby wrote: > > Is it because max_parallel_workers_per_gather now defaults to 2 ? > > > > BTW, I would tentatively expect a change in default to be documented in the > > release notes but can't see that it's. > > 77cd477c4ba885cfa1ba67beaa82e06f2e182b85 > > Oops, you are correct. The PG 10 release notes, which I wrote, should > have mentioned this. :-( I just saw your January response to my October mail.. Maybe it's silly to update PG10 notes 9 months after release.. ..but, any reason not to add to v10 release notes now (I don't know if the web docs would be updated until the next point release?) Justin