Commit b05204ac authored by Tom Lane's avatar Tom Lane

Fix some minor grammatical errors.

parent 9392c405
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/perform.sgml,v 1.22 2002/11/11 20:14:03 petere Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/perform.sgml,v 1.23 2003/01/12 18:42:59 tgl Exp $
--> -->
<chapter id="performance-tips"> <chapter id="performance-tips">
...@@ -600,7 +600,7 @@ SELECT * FROM a, b, c WHERE a.id = b.id AND b.ref = c.id; ...@@ -600,7 +600,7 @@ SELECT * FROM a, b, c WHERE a.id = b.id AND b.ref = c.id;
SELECT * FROM a CROSS JOIN b CROSS JOIN c WHERE a.id = b.id AND b.ref = c.id; SELECT * FROM a CROSS JOIN b CROSS JOIN c WHERE a.id = b.id AND b.ref = c.id;
SELECT * FROM a JOIN (b JOIN c ON (b.ref = c.id)) ON (a.id = b.id); SELECT * FROM a JOIN (b JOIN c ON (b.ref = c.id)) ON (a.id = b.id);
</programlisting> </programlisting>
but the second and third take less time to plan than the first. This effect the second and third take less time to plan than the first. This effect
is not worth worrying about for only three tables, but it can be a is not worth worrying about for only three tables, but it can be a
lifesaver with many tables. lifesaver with many tables.
</para> </para>
...@@ -628,8 +628,8 @@ SELECT * FROM d LEFT JOIN ...@@ -628,8 +628,8 @@ SELECT * FROM d LEFT JOIN
(SELECT * FROM a, b, c WHERE ...) AS ss (SELECT * FROM a, b, c WHERE ...) AS ss
ON (...); ON (...);
</programlisting> </programlisting>
Here, joining D must be the last step in the query plan, but the Here, joining to D must be the last step in the query plan, but the
planner is free to consider various join orders for A, B, C. planner is free to consider various join orders for A, B, and C.
</para> </para>
<para> <para>
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment