diff options
author | Bruce Momjian <bruce@momjian.us> | 2001-05-30 22:58:00 +0000 |
---|---|---|
committer | Bruce Momjian <bruce@momjian.us> | 2001-05-30 22:58:00 +0000 |
commit | e07d894990ee94d27b98022c9ffefbe4d585df26 (patch) | |
tree | 8ddc6f2c20020c23c1612292215616f0ae54391a | |
parent | e05d2460848f7098d69d339393e67e7a51d8f73f (diff) | |
download | postgresql-e07d894990ee94d27b98022c9ffefbe4d585df26.tar.gz postgresql-e07d894990ee94d27b98022c9ffefbe4d585df26.zip |
Update FAQ.
-rw-r--r-- | doc/FAQ | 8 | ||||
-rw-r--r-- | doc/src/FAQ/FAQ.html | 4 |
2 files changed, 6 insertions, 6 deletions
@@ -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 e4989d5a1aa..932b2b7856d 100644 --- a/doc/src/FAQ/FAQ.html +++ b/doc/src/FAQ/FAQ.html @@ -12,7 +12,7 @@ alink="#0000FF"> <H1>Frequently Asked Questions (FAQ) for PostgreSQL</H1> - <P>Last updated: Tue May 22 17:50:25 EDT 2001</P> + <P>Last updated: Wed May 30 18:57:52 EDT 2001</P> <P>Current maintainer: Bruce Momjian (<A href= "mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</A>)<BR> @@ -908,7 +908,7 @@ Maximum number of indexes on a table? unlimited periodically.</P> <P>Indexes are usually not used for <SMALL>ORDER BY</SMALL> - 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.</P> |