From 04fdf73a05a25219be68ea9cff67049f9b6d2dac Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Mon, 20 Aug 2001 20:37:19 +0000 Subject: [PATCH] Update FAQ. --- doc/FAQ | 2 +- doc/src/FAQ/FAQ.html | 13 ++++++------- 2 files changed, 7 insertions(+), 8 deletions(-) diff --git a/doc/FAQ b/doc/FAQ index cac7ad5e58..5e37e45f8f 100644 --- 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 (pgman@candle.pha.pa.us) diff --git a/doc/src/FAQ/FAQ.html b/doc/src/FAQ/FAQ.html index eb6b1fdce6..ce6c0781a0 100644 --- 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 (pgman@candle.pha.pa.us)
@@ -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 @@ -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