|
12 | 12 | alink="#0000FF"> |
13 | 13 | <H1>Frequently Asked Questions (FAQ) for PostgreSQL</H1> |
14 | 14 |
|
15 | | -<P>Last updated:Tue Jul 10 21:01:47 EDT 2001</P> |
| 15 | +<P>Last updated:Mon Aug 20 16:37:10 EDT 2001</P> |
16 | 16 |
|
17 | 17 | <P>Current maintainer: Bruce Momjian (<Ahref= |
18 | 18 | "mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</A>)<BR> |
@@ -338,8 +338,7 @@ <H4><A name="1.9">1.9</A>) How do I find out about known bugs or |
338 | 338 | See our<Ahref="http://www.PostgreSQL.org/docs/todo.html">TODO</A> |
339 | 339 | list for known bugs, missing features, and future plans.</P> |
340 | 340 |
|
341 | | -<H4><Aname="1.10">1.10</A>) How can I learn |
342 | | -<SMALL>SQL</SMALL>?</H4> |
| 341 | +<H4><Aname="1.10">1.10</A>) How can I learn<SMALL>SQL</SMALL>?</H4> |
343 | 342 |
|
344 | 343 | <P>The PostgreSQL book at<Ahref= |
345 | 344 | "http://www.PostgreSQL.org/docs/awbook.html">http://www.PostgreSQL.org/docs/awbook.html</A> |
@@ -626,9 +625,9 @@ <H4><A name="3.6">3.6</A>) Why can't I connect to my database from |
626 | 625 | <H4><Aname="3.7">3.7</A>) How do I tune the database engine for |
627 | 626 | better performance?</H4> |
628 | 627 |
|
629 | | -<P>Certainly, indices can speed up queries. The |
630 | | -<SMALL>EXPLAIN</SMALL>command allows you to see how PostgreSQL is |
631 | | -interpreting your query,and which indices are being used.</P> |
| 628 | +<P>Certainly, indices can speed up queries. The<SMALL>EXPLAIN</SMALL> |
| 629 | + command allows you to see how PostgreSQL is interpreting your query, |
| 630 | + and which indices are being used.</P> |
632 | 631 |
|
633 | 632 | <P>If you are doing a lot of<SMALL>INSERTs</SMALL>, consider doing |
634 | 633 | them in a large batch using the<SMALL>COPY</SMALL> command. This |
@@ -900,7 +899,7 @@ <H4><A name="4.9">4.9</A>) My queries are slow or don't make use of |
900 | 899 | because a sequential scan would be faster.</P> |
901 | 900 |
|
902 | 901 | <P>For column-specific optimization statistics, use<SMALL>VACUUM |
903 | | - ANALYZE.</SMALL><SMALL>VACUUM ANALYZE</SMALL> is important for |
| 902 | + ANALYZE.</SMALL>V<SMALL>ACUUM ANALYZE</SMALL> is important for |
904 | 903 | complex multijoin queries, so the optimizer can estimate the number |
905 | 904 | of rows returned from each table, and choose the proper join order. |
906 | 905 | The backend does not keep track of column statistics on its own, so |
|