On Mon, Mar 6, 2017 at 4:57 PM, Michael Banck <michael.ba...@credativ.de> wrote: > Hi, > > On Thu, Feb 16, 2017 at 08:14:28AM +0530, Amit Kapila wrote: >> On Thu, Feb 16, 2017 at 12:27 AM, Robert Haas <robertmh...@gmail.com> wrote: >> > On Wed, Feb 15, 2017 at 1:39 PM, Robert Haas <robertmh...@gmail.com> wrote: >> >> On Wed, Feb 15, 2017 at 7:11 AM, Amit Kapila <amit.kapil...@gmail.com> >> >> wrote:> >> >>> support related patch. In anycase, to avoid confusion I am attaching >> >>> all the three patches with this e-mail. >> >> >> >> Committed guc_parallel_index_scan_v1.patch, with changes to the >> >> documentation and GUC descriptions. >> > >> > And committed parallel_index_opt_exec_support_v10.patch as well, with >> > a couple of minor tweaks. >> >> Thanks a lot! I think this is a big step forward for parallelism in >> PostgreSQL. Now, we have another way to drive parallel scans and I >> hope many more queries can use parallelism. > > Shouldn't the chapter 15.3 "Parallel Plans" in the documentation be > updated for this as well, or is this going to be taken care as a batch > at the ned of the development cycle, pending other added parallization > features? >
Robert mentioned up thread that it is better to update it once at end rather than with each feature. -- With Regards, Amit Kapila. EnterpriseDB: http://www.enterprisedb.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
