| From: | Dilip kumar <dilip(dot)kumar(at)huawei(dot)com> |
|---|---|
| To: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Jan Lentfer <Jan(dot)Lentfer(at)web(dot)de>, Euler Taveira <euler(at)timbira(dot)com(dot)br> |
| Subject: | Re: TODO : Allow parallel cores to be used by vacuumdb [ WIP ] |
| Date: | 2014-06-24 05:45:06 |
| Message-ID: | 4205E661176A124FAF891E0A6BA9135266335B7E@szxeml509-mbs.china.huawei.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 24 June 2014 11:02 Jeff Wrote,
>I mean that the other commit, the one conflicting with your patch, is still not finished. It probably would not have been committed if we realized the problem at the time. That other patch runs analyze in stages at
> different settings of default_statistics_target, but it has the loops in the wrong order, so it analyzes one database in all three stages, then moves to the next database. I think that these two changes are going to
> interact with each other. But I can't predict right now what that interaction will look like. So it is hard for me to evaluate your patch, until the other one is resolved.
>Normally I would evaluate your patch in isolation, but since the conflicting patch is already committed (and is in the 9.4 branch) that would probably not be very useful in this case.
Oh k, Got your point, I will also try to think how these two patch can interact together..
Regards,
Dilip
| From | Date | Subject | |
|---|---|---|---|
| Next Message | furuyao | 2014-06-24 06:18:10 | Re: pg_receivexlog add synchronous mode |
| Previous Message | Amit Kapila | 2014-06-24 05:37:48 | Re: Wait free LW_SHARED acquisition - v0.2 |