pgsql-performance(at)postgresql(dot)org, "Jim C(dot) Nasby" <decibel(at)decibel(dot)org>, Simon Riggs <simon(at)2ndquadrant(dot)com>, David Brown <time(at)bigpond(dot)net(dot)au>
>> I've seen cases where it seems the >> planer doesn't think it'll be getting a unique value or a small set of >> values even though stats indicates that it should be.
A test case exhibiting the problem would be helpful.