On Fri, Mar 21, 2014 at 12:48 AM, Dilip kumar <dilip.ku...@huawei.com> wrote: > On 16 January 2014 19:53, Euler Taveira Wrote, > >> > >> >> For the case where you have tables of varying size this would lead >> to a reduced overall processing time as it prevents large (read: long >> processing time) tables to be processed in the last step. While >> processing large tables at first and filling up "processing slots/jobs" >> when they get free with smaller tables one after the other would safe >> overall execution time. >> > Good point, I have made the change and attached the modified patch. >> > >> Don't you submit it for a CF, do you? Is it too late for this CF? > > Attached the latest updated patch > 1. Rebased the patch to current GIT head. > 2. Doc is updated. > 3. Supported parallel execution for all db option also.
This patch needs to be rebased after the analyze-in-stages patch, c92c3d50d7fbe7391b5fc864b44434. Although that patch still needs to some work itself, despite being committed, as still loops over the stages for each db, rather than the dbs for each stage. So I don't know if this patch is really reviewable at this point, as it is not clear how those things are going to interact with each other. Cheers, Jeff -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
