File tree Expand file tree Collapse file tree 2 files changed +7
-7
lines changed Expand file tree Collapse file tree 2 files changed +7
-7
lines changed Original file line number Diff line number Diff line change 1
1
2
2
Frequently Asked Questions (FAQ) for PostgreSQL
3
3
4
- Last updated: Thu Apr 13 08:14:25 EDT 2006
4
+ Last updated: Thu Apr 13 08:20:04 EDT 2006
5
5
6
6
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
7
7
569
569
570
570
Indexes are normally not used for ORDER BY or to perform joins. A
571
571
sequential scan followed by an explicit sort is usually faster than an
572
- index scan of a large table.
573
- However, LIMIT combined with ORDER BY often will use an index because
574
- only a small portion of the table is returned.
572
+ index scan of a large table. However, LIMIT combined with ORDER BY
573
+ often will use an index because only a small portion of the table is
574
+ returned.
575
575
576
576
If you believe the optimizer is incorrect in choosing a sequential
577
577
scan, use SET enable_seqscan TO 'off' and run query again to see if an
Original file line number Diff line number Diff line change 10
10
alink ="#0000ff ">
11
11
< H1 > Frequently Asked Questions (FAQ) for PostgreSQL</ H1 >
12
12
13
- < P > Last updated: Thu Apr 13 08:14:25 EDT 2006</ P >
13
+ < P > Last updated: Thu Apr 13 08:20:04 EDT 2006</ P >
14
14
15
15
< P > Current maintainer: Bruce Momjian (< A href =
16
16
"mailto:pgman@candle.pha.pa.us "> pgman@candle.pha.pa.us</ A > )
@@ -361,7 +361,7 @@ <H3 id="item1.11">1.11) How can I learn
361
361
< LI > < A href ="http://www.intermedia.net/support/sql/sqltut.shtm "> http://www.intermedia.net/support/sql/sqltut.shtm</ A >
362
362
</ LI >
363
363
< LI >
364
- < A href ="http://sqlcourse.com/ "> http://sqlcourse.com</ A > </ P >
364
+ < A href ="http://sqlcourse.com/ "> http://sqlcourse.com</ A >
365
365
</ LI >
366
366
< LI >
367
367
< A href ="http://www.w3schools.com/sql/default.asp "> http://www.w3schools.com/sql/default.asp</ A >
@@ -748,7 +748,7 @@ <H3 id="item4.6">4.6) Why are my queries slow? Why don't they
748
748
749
749
< P > Indexes are normally not used for < SMALL > ORDER BY</ SMALL > or to
750
750
perform joins. A sequential scan followed by an explicit sort is
751
- usually faster than an index scan of a large table.</ P >
751
+ usually faster than an index scan of a large table.
752
752
However, < SMALL > LIMIT</ SMALL > combined with < SMALL > ORDER BY</ SMALL >
753
753
often will use an index because only a small portion of the table
754
754
is returned.</ P >
You can’t perform that action at this time.
0 commit comments