mirrors
/
postgres
mirror of https://github.com/postgres/postgres
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Update FAQ.

This commit is contained in:
Bruce Momjian 2001-05-30 22:58:00 +00:00
parent e05d246084
commit e07d894990
2 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
doc/FAQ
View File

@ -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

4
doc/src/FAQ/FAQ.html
View File

@ -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>