|
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 (<Ahref=
|
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><Ahref="http://www.intermedia.net/support/sql/sqltut.shtm">http://www.intermedia.net/support/sql/sqltut.shtm</A>
|
362 | 362 | </LI>
|
363 | 363 | <LI>
|
364 |
| -<Ahref="http://sqlcourse.com/">http://sqlcourse.com</A></P> |
| 364 | +<Ahref="http://sqlcourse.com/">http://sqlcourse.com</A> |
365 | 365 | </LI>
|
366 | 366 | <LI>
|
367 | 367 | <Ahref="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>
|
|