Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commitdcdf738

Browse files
committed
Fix HTML markup.
1 parent2aca4e8 commitdcdf738

File tree

2 files changed

+7
-7
lines changed

2 files changed

+7
-7
lines changed

‎doc/FAQ

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11

22
Frequently Asked Questions (FAQ) for PostgreSQL
33

4-
Last updated: Thu Apr 13 08:14:25 EDT 2006
4+
Last updated: Thu Apr 13 08:20:04 EDT 2006
55

66
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
77

@@ -569,9 +569,9 @@
569569

570570
Indexes are normally not used for ORDER BY or to perform joins. A
571571
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 BYoften will use an index because
574-
only a small portion of the table isreturned.
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.
575575

576576
If you believe the optimizer is incorrect in choosing a sequential
577577
scan, use SET enable_seqscan TO 'off' and run query again to see if an

‎doc/src/FAQ/FAQ.html

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@
1010
alink="#0000ff">
1111
<H1>Frequently Asked Questions (FAQ) for PostgreSQL</H1>
1212

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>
1414

1515
<P>Current maintainer: Bruce Momjian (<Ahref=
1616
"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
361361
<LI><Ahref="http://www.intermedia.net/support/sql/sqltut.shtm">http://www.intermedia.net/support/sql/sqltut.shtm</A>
362362
</LI>
363363
<LI>
364-
<Ahref="http://sqlcourse.com/">http://sqlcourse.com</A></P>
364+
<Ahref="http://sqlcourse.com/">http://sqlcourse.com</A>
365365
</LI>
366366
<LI>
367367
<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
748748

749749
<P>Indexes are normally not used for<SMALL>ORDER BY</SMALL> or to
750750
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.
752752
However,<SMALL>LIMIT</SMALL> combined with<SMALL>ORDER BY</SMALL>
753753
often will use an index because only a small portion of the table
754754
is returned.</P>

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp