<div class="WordSection1"><p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">On</span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"></span><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">24June 2014 11:02 Jeff Wrote,</span><p
class="MsoNormal"><spanstyle="font-size:10.0pt;font-family:"Tahoma","sans-serif""> </span><p class="MsoNormal">>I
meanthat the other commit, the one conflicting with your patch, is still not finished. It probably would not have been
committedif we realized the problem at the time. That other patch runs analyze in stages at <p class="MsoNormal">>
differentsettings of default_statistics_target, but it has the loops in the wrong order, so it analyzes one database in
allthree stages, then moves to the next database. I think that these two changes are going to<p class="MsoNormal">>
interactwith each other. But I can't predict right now what that interaction will look like. So it is hard for me to
evaluateyour patch, until the other one is resolved.<p class="MsoNormal"> <p class="MsoNormal">>Normally I would
evaluateyour patch in isolation, but since the conflicting patch is already committed (and is in the 9.4 branch) that
wouldprobably not be very useful in this case.<p class="MsoNormal"> <p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> </span><pclass="MsoNormal"><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">Ohk, Got your point, I will also try to think how these two
patchcan interact together.. </span><p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><pclass="MsoNormal"><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">Regards,</span><pclass="MsoNormal"><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">Dilip</span></div>