From dcdf738abb013082294b9a8afb15b8405e042d47 Mon Sep 17 00:00:00 2001
From: Bruce Momjian <bruce@momjian.us>
Date: Thu, 13 Apr 2006 12:20:36 +0000
Subject: [PATCH] Fix HTML markup.
---
doc/FAQ | 8 ++++----
doc/src/FAQ/FAQ.html | 6 +++---
2 files changed, 7 insertions(+), 7 deletions(-)
diff --git a/doc/FAQ b/doc/FAQ
index 668d11c2530..d2c686839d1 100644
--- a/doc/FAQ
+++ b/doc/FAQ
@@ -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
diff --git a/doc/src/FAQ/FAQ.html b/doc/src/FAQ/FAQ.html
index 9ec6075593f..55f087379ea 100644
--- a/doc/src/FAQ/FAQ.html
+++ b/doc/src/FAQ/FAQ.html
@@ -10,7 +10,7 @@
alink="#0000ff">
<H1>Frequently Asked Questions (FAQ) for PostgreSQL</H1>
- <P>Last updated: Thu Apr 13 08:14:25 EDT 2006</P>
+ <P>Last updated: Thu Apr 13 08:20:04 EDT 2006</P>
<P>Current maintainer: Bruce Momjian (<A href=
"mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</A>)
@@ -361,7 +361,7 @@
<LI> <A href="http://www.intermedia.net/support/sql/sqltut.shtm">http://www.intermedia.net/support/sql/sqltut.shtm</A>
</LI>
<LI>
- <A href="http://sqlcourse.com/">http://sqlcourse.com</A></P>
+ <A href="http://sqlcourse.com/">http://sqlcourse.com</A>
</LI>
<LI>
<A href="http://www.w3schools.com/sql/default.asp">http://www.w3schools.com/sql/default.asp</A>
@@ -748,7 +748,7 @@ table?</TD><TD>unlimited</TD></TR>
<P>Indexes are normally not used for <SMALL>ORDER BY</SMALL> or to
perform joins. A sequential scan followed by an explicit sort is
- usually faster than an index scan of a large table.</P>
+ usually faster than an index scan of a large table.
However, <SMALL>LIMIT</SMALL> combined with <SMALL>ORDER BY</SMALL>
often will use an index because only a small portion of the table
is returned.</P>
--
GitLab