aboutsummaryrefslogtreecommitdiff
path: root/doc/FAQ
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>2001-05-30 22:58:00 +0000
committerBruce Momjian <bruce@momjian.us>2001-05-30 22:58:00 +0000
commite07d894990ee94d27b98022c9ffefbe4d585df26 (patch)
tree8ddc6f2c20020c23c1612292215616f0ae54391a /doc/FAQ
parente05d2460848f7098d69d339393e67e7a51d8f73f (diff)
downloadpostgresql-e07d894990ee94d27b98022c9ffefbe4d585df26.tar.gz
postgresql-e07d894990ee94d27b98022c9ffefbe4d585df26.zip
Update FAQ.
Diffstat (limited to 'doc/FAQ')
-rw-r--r--doc/FAQ8
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/FAQ b/doc/FAQ
index 9b8539da9cb..f59d74ff9a3 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