aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2003-01-12 18:42:59 +0000
committerTom Lane <tgl@sss.pgh.pa.us>2003-01-12 18:42:59 +0000
commitb05204ac8a36ebe4f68823fdc47be2cde294621b (patch)
tree7138be49ece4567b9debd724cd8df146fc50ab98
parent9392c40553dac125a7ff63d11e513e8b006a0c83 (diff)
downloadpostgresql-b05204ac8a36ebe4f68823fdc47be2cde294621b.tar.gz
postgresql-b05204ac8a36ebe4f68823fdc47be2cde294621b.zip
Fix some minor grammatical errors.
-rw-r--r--doc/src/sgml/perform.sgml8
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/src/sgml/perform.sgml b/doc/src/sgml/perform.sgml
index fb2dd96b037..4c150d50220 100644
--- a/doc/src/sgml/perform.sgml
+++ b/doc/src/sgml/perform.sgml
@@ -1,5 +1,5 @@
<!--
-$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">
@@ -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 JOIN (b JOIN c ON (b.ref = c.id)) ON (a.id = b.id);
</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
lifesaver with many tables.
</para>
@@ -628,8 +628,8 @@ SELECT * FROM d LEFT JOIN
(SELECT * FROM a, b, c WHERE ...) AS ss
ON (...);
</programlisting>
- Here, joining D must be the last step in the query plan, but the
- planner is free to consider various join orders for A, B, C.
+ 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, and C.
</para>
<para>