On Wed, Jun 20, 2018 at 8:43 PM, Bruce Momjian <br...@momjian.us> 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 <rh...@postgresql.org> > 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
