Comment 21 for bug 1768022

Thanks for the pointer Bill, that's definitely a best case for this fix. I had that bug in the back of my mind for a little bit but since I didn't see anything with that kind of wildly inaccurate row estimates I didn't think to look at it that closely. (Ah, but Pg 9.3 didn't break out plan/exec time, at least not in Chris's paste...)