Update FAQ.

diff --git a/doc/FAQ b/doc/FAQ
index cac7ad5e585ad251c1c2cefffa705f380d74f116..5e37e45f8fbea8d973e2ae0b0eeb02bdbd54334c 100644 (file)
--- a/doc/FAQ
+++ b/doc/FAQ
@@ -1,7 +1,7 @@
 
                 Frequently Asked Questions (FAQ) for PostgreSQL
                                        
-   Last updated: Tue Jul 10 21:01:47 EDT 2001
+   Last updated: Mon Aug 20 16:37:10 EDT 2001
    
    Current maintainer: Bruce Momjian ([email protected])
    

diff --git a/doc/src/FAQ/FAQ.html b/doc/src/FAQ/FAQ.html
index eb6b1fdce62a60fa1bac179d5d70e0c6e697ac1a..ce6c0781a095a6699e828c5e57b214ac2184e1ab 100644 (file)
--- a/doc/src/FAQ/FAQ.html
+++ b/doc/src/FAQ/FAQ.html
@@ -12,7 +12,7 @@
   alink="#0000FF">
     Frequently Asked Questions (FAQ) for PostgreSQL
 
-    Last updated: Tue Jul 10 21:01:47 EDT 2001
+    Last updated: Mon Aug 20 16:37:10 EDT 2001
 
     Current maintainer: Bruce Momjian (
     "mailto:[email protected]">[email protected])
@@ -338,8 +338,7 @@
     See our TODO
     list for known bugs, missing features, and future plans.
 
-    1.10) How can I learn
-    SQL?
+    1.10) How can I learn SQL?
 
     The PostgreSQL book at 
     "http://www.PostgreSQL.org/docs/awbook.html">http://www.PostgreSQL.org/docs/awbook.html
@@ -626,9 +625,9 @@
     3.7) How do I tune the database engine for
     better performance?
 
-    Certainly, indices can speed up queries. The
-    EXPLAIN command allows you to see how PostgreSQL is
-    interpreting your query, and which indices are being used.
+    Certainly, indices can speed up queries. The EXPLAIN
+    command allows you to see how PostgreSQL is interpreting your query,
+    and which indices are being used.
 
     If you are doing a lot of INSERTs, consider doing
     them in a large batch using the COPY command. This
@@ -900,7 +899,7 @@ Maximum number of indexes on a table?    unlimited
     because a sequential scan would be faster.
 
     For column-specific optimization statistics, use VACUUM
-    ANALYZE. VACUUM ANALYZE is important for
+    ANALYZE. VACUUM ANALYZE is important for
     complex multijoin queries, so the optimizer can estimate the number
     of rows returned from each table, and choose the proper join order.
     The backend does not keep track of column statistics on its own, so