From e07d894990ee94d27b98022c9ffefbe4d585df26 Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Wed, 30 May 2001 22:58:00 +0000 Subject: [PATCH] Update FAQ. --- doc/FAQ | 8 ++++---- doc/src/FAQ/FAQ.html | 4 ++-- 2 files changed, 6 insertions(+), 6 deletions(-) diff --git a/doc/FAQ b/doc/FAQ index 9b8539da9c..f59d74ff9a 100644 --- a/doc/FAQ +++ b/doc/FAQ @@ -1,7 +1,7 @@ Frequently Asked Questions (FAQ) for PostgreSQL - Last updated: Tue May 22 17:50:25 EDT 2001 + Last updated: Wed May 30 18:57:52 EDT 2001 Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us) @@ -709,9 +709,9 @@ Maximum number of indexes on a table? unlimited column statistics on its own, so VACUUM ANALYZE must be run to collect them periodically. - Indexes are usually not used for ORDER BY operations: a sequential - scan followed by an explicit sort is faster than an indexscan of all - tuples of a large table, because it takes fewer disk accesses. + Indexes are usually not used for ORDER BY or joins: a sequential scan + followed by an explicit sort is faster than an indexscan of all tuples + of a large table, because it takes fewer disk accesses. When using wild-card operators such as LIKE or ~, indices can only be used if the beginning of the search is anchored to the start of the diff --git a/doc/src/FAQ/FAQ.html b/doc/src/FAQ/FAQ.html index e4989d5a1a..932b2b7856 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 May 22 17:50:25 EDT 2001

+

Last updated: Wed May 30 18:57:52 EDT 2001

Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
@@ -908,7 +908,7 @@ Maximum number of indexes on a table? unlimited periodically.

Indexes are usually not used for ORDER BY - operations: a sequential scan followed by an explicit sort is + or joins: a sequential scan followed by an explicit sort is faster than an indexscan of all tuples of a large table, because it takes fewer disk accesses.