diff options
| author | Bruce Momjian <bruce@momjian.us> | 2006-04-13 12:20:36 +0000 |
|---|---|---|
| committer | Bruce Momjian <bruce@momjian.us> | 2006-04-13 12:20:36 +0000 |
| commit | dcdf738abb013082294b9a8afb15b8405e042d47 (patch) | |
| tree | c02125e3db8372be9415b9db374961fe76723274 /doc/FAQ | |
| parent | 2aca4e84af27acd09291438b480ede69a4c21e2d (diff) | |
Fix HTML markup.
Diffstat (limited to 'doc/FAQ')
| -rw-r--r-- | doc/FAQ | 8 |
1 files changed, 4 insertions, 4 deletions
@@ -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 |