Tom Lane <tgl@sss.pgh.pa.us> writes:
> "Jim C. Nasby" <jnasby@pervasive.com> writes:
>
>> How many cycles are we talking about here? Is it even worth the GUC?
>
> I think so. On simple queries the optimization will *never* fire,
> and there's no point in doing the search. People who are running
> complex queries will want to turn it on, but the mysql-equivalent
> crew will just find it a waste of cycles.
The other class of people who will find this kind of thing useful are those
using automatically generated queries. Frequently you end up with redundant
clauses or "unreachable" clauses that you hope the database will be able to
see through.
Having to enable that intelligence with a GUC is fine though since those users
could just enable it even if they aren't using partitioning. That said I
expect that eventually any option we add whose only purpose is it to enable
some intelligence in the optimizer will become standard.
-- Gregory Stark EnterpriseDB http://www.enterprisedb.com
