Re: [SQL] Good Optimization

> Also if the optimizer works similar to Oracle then the order of
> where statements would also help in actual performance.  I'm mostly a
> lurker on this list but have never seen anything about this issue.
>    When using Oracle, and won't it be nice when people mention PostgreSQL
> functionality when comparing other databases, the statements at the
> bottom should be the most restrictive and joins should be near the top.
> 
>     select * 
>       from po,tickets
>      where po_id=material_po
>        and po_id=8888 ;
> 
> Would be the best.  Whereas
> 
>     select *
>       from po,tickets
>      where po_id=8888
>        and po_id=material_po;
> 
> would do the join then select those tuples that have a po_id of 8888.
> 
> Of course this is probably what PostgreSQL is doing already without a
> requirement for the positioning.

This is not your mother's database.  We don't care about statement
ordering.  :-)


--  Bruce Momjian                        |  http://www.op.net/~candle maillist@candle.pha.pa.us            |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania19026