mirror of
https://github.com/postgres/postgres.git
synced 2025-07-27 12:41:57 +03:00
Backpatch FAQ changes to 8.1.X.
This commit is contained in:
12
doc/FAQ
12
doc/FAQ
@ -1,7 +1,7 @@
|
||||
|
||||
Frequently Asked Questions (FAQ) for PostgreSQL
|
||||
|
||||
Last updated: Sun Feb 12 12:15:49 EST 2006
|
||||
Last updated: Fri Feb 24 09:59:35 EST 2006
|
||||
|
||||
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
|
||||
|
||||
@ -569,14 +569,8 @@
|
||||
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. In fact, though MAX()
|
||||
and MIN() don't use indexes, it is possible to retrieve such values
|
||||
using an index with ORDER BY and LIMIT:
|
||||
SELECT col
|
||||
FROM tab
|
||||
ORDER BY col [ DESC ]
|
||||
LIMIT 1;
|
||||
|
||||
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
|
||||
index scan is indeed faster.
|
||||
|
Reference in New Issue
Block a user