From e1caa9040676de4c701294c55c9d819e93ed99cb Mon Sep 17 00:00:00 2001
From: Bruce Momjian <bruce@momjian.us>
Date: Tue, 9 Oct 2007 20:13:11 +0000
Subject: Add mention of full text indexing for word searches.

---
 doc/src/FAQ/FAQ.html | 9 +++------
 1 file changed, 3 insertions(+), 6 deletions(-)

(limited to 'doc/src')

diff --git a/doc/src/FAQ/FAQ.html b/doc/src/FAQ/FAQ.html
index f8b797fb0d4..e829f083147 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: Tue Oct  9 16:07:30 EDT 2007</P>
+    <P>Last updated: Tue Oct  9 16:13:00 EDT 2007</P>
 
     <P>Current maintainer: Bruce Momjian (<A href=
     "mailto:bruce@momjian.us">bruce@momjian.us</A>)
@@ -784,14 +784,11 @@ table?</TD><TD>unlimited</TD></TR>
     <i>initdb</i> because it is not possible to know the next-greatest
     character in a non-C locale.  You can create a special
     <CODE>text_pattern_ops</CODE> index for such cases that work only
-    for <SMALL>LIKE</SMALL> indexing.
+    for <SMALL>LIKE</SMALL> indexing.  It is also possible to use
+    full text indexing for word searches.
     </LI>
     </UL>
 
-    <P>In pre-8.0 releases, indexes often can not be used unless the data
-    types exactly match the index's column types.  This was particularly
-    true of int2, int8, and numeric column indexes.</P>
-
     <H3 id="item4.7">4.7) How do I see how the query optimizer is
     evaluating my query?</H3>
 
-- 
cgit v1.2.3