Skip to content

P
Postgres FD Implementation
Commit dcdf738a authored by Bruce Momjian's avatar Bruce Momjian
Browse files
Options

Fix HTML markup.

parent 2aca4e84
Show whitespace changes
Inline Side-by-side
Showing with 7 additions and 7 deletions
doc/FAQ
View file @ dcdf738a
Frequently Asked Questions (FAQ) for PostgreSQL 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) Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
...@@ -569,9 +569,9 @@ ...@@ -569,9 +569,9 @@
Indexes are normally not used for ORDER BY or to perform joins. A 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 sequential scan followed by an explicit sort is usually faster than an
index scan of a large table. index scan of a large table. However, LIMIT combined with ORDER BY
However, LIMIT combined with ORDER BY often will use an index because often will use an index because only a small portion of the table is
only a small portion of the table is returned. returned.
If you believe the optimizer is incorrect in choosing a sequential 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 scan, use SET enable_seqscan TO 'off' and run query again to see if an
......
doc/src/FAQ/FAQ.html
View file @ dcdf738a
...@@ -10,7 +10,7 @@ ...@@ -10,7 +10,7 @@
alink="#0000ff"> alink="#0000ff">
<H1>Frequently Asked Questions (FAQ) for PostgreSQL</H1> <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= <P>Current maintainer: Bruce Momjian (<A href=
"mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</A>) "mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</A>)
...@@ -361,7 +361,7 @@ ...@@ -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> <A href="http://www.intermedia.net/support/sql/sqltut.shtm">http://www.intermedia.net/support/sql/sqltut.shtm</A>
</LI> </LI>
<LI> <LI>
<A href="http://sqlcourse.com/">http://sqlcourse.com</A></P> <A href="http://sqlcourse.com/">http://sqlcourse.com</A>
</LI> </LI>
<LI> <LI>
<A href="http://www.w3schools.com/sql/default.asp">http://www.w3schools.com/sql/default.asp</A> <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> ...@@ -748,7 +748,7 @@ table?</TD><TD>unlimited</TD></TR>
<P>Indexes are normally not used for <SMALL>ORDER BY</SMALL> or to <P>Indexes are normally not used for <SMALL>ORDER BY</SMALL> or to
perform joins. A sequential scan followed by an explicit sort is 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> However, <SMALL>LIMIT</SMALL> combined with <SMALL>ORDER BY</SMALL>
often will use an index because only a small portion of the table often will use an index because only a small portion of the table
is returned.</P> is returned.</P>
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment