This problem appears to have been introduced by the
Generation Query Planner]
change of version 3.8.0, and specifically check-in
[0fe31f60cadc5fe5] (2013-06-21).  This problem was found in the wild
and was brought to the attention of the developers via a private
email message.