diff --git a/doc/FAQ b/doc/FAQ index 668d11c253..d2c686839d 100644 --- a/doc/FAQ +++ b/doc/FAQ @@ -1,7 +1,7 @@ Frequently Asked Questions (FAQ) for PostgreSQL - Last updated: Thu Apr 13 08:14:25 EDT 2006 + Last updated: Thu Apr 13 08:20:04 EDT 2006 Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us) @@ -569,9 +569,9 @@ Indexes are normally not used for ORDER BY or to perform joins. A sequential scan followed by an explicit sort is usually faster than an - index scan of a large table. - However, LIMIT combined with ORDER BY often will use an index because - only a small portion of the table is returned. + index scan of a large table. However, LIMIT combined with ORDER BY + often will use an index because only a small portion of the table is + returned. If you believe the optimizer is incorrect in choosing a sequential scan, use SET enable_seqscan TO 'off' and run query again to see if an diff --git a/doc/src/FAQ/FAQ.html b/doc/src/FAQ/FAQ.html index 9ec6075593..55f087379e 100644 --- a/doc/src/FAQ/FAQ.html +++ b/doc/src/FAQ/FAQ.html @@ -10,7 +10,7 @@ alink="#0000ff">
Last updated: Thu Apr 13 08:14:25 EDT 2006
+Last updated: Thu Apr 13 08:20:04 EDT 2006
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us) @@ -361,7 +361,7 @@
Indexes are normally not used for ORDER BY or to perform joins. A sequential scan followed by an explicit sort is - usually faster than an index scan of a large table.
+ usually faster than an index scan of a large table. However, LIMIT combined with ORDER BY often will use an index because only a small portion of the table is returned.