> Stephan Szabo <sszabo@megazone23.bigpanda.com> writes:
>> It's basically converted it into a three way join.
>
> More to the point, an *unconstrained* join between "claimsum2001
> as claimsum2001" and the intended joined table. The reason it
> ran for so long was it was generating a huge number of rows ---
> as many as would be in the cross product.
Would it be possible to have some sort of configurable limit on this:
max_result_set_size = 10,000,000
max_result_set_action = ignore | debug | warn | error
The planner knows how many rows it's expecting to return, and a warning
message would show up unconstrained queries like this.
- Richard Huxton
