> > 2. Should we keep the default value of GUC to on or off? It is > > currently off. I am fine keeping it off for this release and we can > > always turn it on in the later releases if required. Having said that, > > I see the value in keeping it on because in many cases Insert ... > > Select will be used for large data and there we will see a benefit of > > parallelism and users facing trouble (who have a very large number of > > partitions with less data to query) can still disable the parallel > > insert for that particular table. Also, the other benefit of keeping > > it on till at least the beta period is that this functionality will > > get tested and if we found reports of regression then we can turn it > > off for this release as well. > > > > Thoughts? > > IMHO, we should keep it on because in most of the cases it is going the give > benefit to the user, and if for some specific scenario where a table has a > lot of > partition then it can be turned off using reloption. And, if for some users > most > of the tables are like that where they always have a lot of partition then > the user > can turn it off using guc. > I think your suggestion makes sense. If no one have other opinions, I will post a new version set default enable_parallel_insert=on soon.
Best regards, houzj
