8000 Add mention of full text indexing for word searches. · postgres/postgres@e1caa90 · GitHub
[go: up one dir, main page]
Skip to content

Commit e1caa90

Browse files
bmomjianbmomjian
committed
Add mention of full text indexing for word searches.
1 parent db962bb commit e1caa90

File tree

2 files changed

+6
-12
lines changed

2 files changed

+6
-12
lines changed

‎doc/FAQ

Lines changed: 3 additions & 6 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: Tue Oct 9 16:07:30 EDT 2007
4+
Last updated: Tue Oct 9 16:13:00 EDT 2007
55

66
Current maintainer: Bruce Momjian (bruce@momjian.us)
77

@@ -600,12 +600,9 @@
600600
* The default C locale must be used during initdb because it is not
601601
possible to know the next-greatest character in a non-C locale.
602602
You can create a special text_pattern_ops index for such cases
603-
that work only for LIKE indexing.
603+
that work only for LIKE indexing. It is also possible to use full
604+
text indexing for word searches.
604605

605-
In pre-8.0 releases, indexes often can not be used unless the data
606-
types exactly match the index's column types. This was particularly
607-
true of int2, int8, and numeric column indexes.
608-
609606
4.7) How do I see how the query optimizer is evaluating my query?
610607

611< 8000 /code>608
See the EXPLAIN manual page.

‎doc/src/FAQ/FAQ.html

Lines changed: 3 additions & 6 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: Tue Oct 9 16:07:30 EDT 2007</P>
13+
<P>Last updated: Tue Oct 9 16:13:00 EDT 2007</P>
1414

1515
<P>Current maintainer: Bruce Momjian (<A href=
1616
"mailto:bruce@momjian.us">bruce@momjian.us</A>)
@@ -784,14 +784,11 @@ <H3 id="item4.6">4.6) Why are my queries slow? Why don't they
784784
<i>initdb</i> because it is not possible to know the next-greatest
785785
character in a non-C locale. You can create a special
786786
<CODE>text_pattern_ops</CODE> index for such cases that work only
787-
for <SMALL>LIKE</SMALL> indexing.
787+
for <SMALL>LIKE</SMALL> indexing. It is also possible to use
788+
full text indexing for word searches.
788789
</LI>
789790
</UL>
790791

791-
<P>In pre-8.0 releases, indexes often can not be used unless the data
792-
types exactly match the index's column types. This was particularly
793-
true of int2, int8, and numeric column indexes.</P>
794-
795792
<H3 id="item4.7">4.7) How do I see how the query optimizer is
796793
evaluating my query?</H3>
797794

0 commit comments

Comments
 (0)
0