|
1 | 1 | <!-- |
2 | | -$Header: /cvsroot/pgsql/doc/src/sgml/perform.sgml,v 1.22 2002/11/11 20:14:03 petere Exp $ |
| 2 | +$Header: /cvsroot/pgsql/doc/src/sgml/perform.sgml,v 1.23 2003/01/12 18:42:59 tgl Exp $ |
3 | 3 | --> |
4 | 4 |
|
5 | 5 | <chapter id="performance-tips"> |
@@ -600,7 +600,7 @@ SELECT * FROM a, b, c WHERE a.id = b.id AND b.ref = c.id; |
600 | 600 | SELECT * FROM a CROSS JOIN b CROSS JOIN c WHERE a.id = b.id AND b.ref = c.id; |
601 | 601 | SELECT * FROM a JOIN (b JOIN c ON (b.ref = c.id)) ON (a.id = b.id); |
602 | 602 | </programlisting> |
603 | | -butthe second and third take less time to plan than the first. This effect |
| 603 | + the second and third take less time to plan than the first. This effect |
604 | 604 | is not worth worrying about for only three tables, but it can be a |
605 | 605 | lifesaver with many tables. |
606 | 606 | </para> |
@@ -628,8 +628,8 @@ SELECT * FROM d LEFT JOIN |
628 | 628 | (SELECT * FROM a, b, c WHERE ...) AS ss |
629 | 629 | ON (...); |
630 | 630 | </programlisting> |
631 | | - Here, joining D must be the last step in the query plan, but the |
632 | | - planner is free to consider various join orders for A, B, C. |
| 631 | + Here, joiningtoD must be the last step in the query plan, but the |
| 632 | + planner is free to consider various join orders for A, B,andC. |
633 | 633 | </para> |
634 | 634 |
|
635 | 635 | <para> |
|