From 95d8b6a7b4e1c50330ef28ec4922e940a6b44979 Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Fri, 19 May 2006 03:34:49 +0000 Subject: Backpatch FAQs to 8.1.X. --- doc/src/FAQ/FAQ.html | 27 +++++++++++++++++---------- 1 file changed, 17 insertions(+), 10 deletions(-) (limited to 'doc/src/FAQ') diff --git a/doc/src/FAQ/FAQ.html b/doc/src/FAQ/FAQ.html index c3512b61354..55f087379ea 100644 --- a/doc/src/FAQ/FAQ.html +++ b/doc/src/FAQ/FAQ.html @@ -10,7 +10,7 @@ alink="#0000ff">
Last updated: Wed Apr 12 16:03:39 EDT 2006
+Last updated: Thu Apr 13 08:20:04 EDT 2006
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us) @@ -356,14 +356,21 @@ Bowman, Judith S., et al., Addison-Wesley. Others like The Complete Reference SQL, Groff et al., McGraw-Hill.
-There is also a nice tutorial at http://www.intermedia.net/support/sql/sqltut.shtm, - at - http://ourworld.compuserve.com/homepages/graeme_birchall/HTM_COOK.HTM, - and at http://sqlcourse.com.
- +There are also many nice tutorials available online: +
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.
+ 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. -- cgit v1.2.3