summaryrefslogtreecommitdiff
path: root/doc/FAQ
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>2007-10-09 20:13:11 +0000
committerBruce Momjian <bruce@momjian.us>2007-10-09 20:13:11 +0000
commite1caa9040676de4c701294c55c9d819e93ed99cb (patch)
treef982ceada9b15ecb0d51cf0450236d24a9b48fa3 /doc/FAQ
parentdb962bb14d655ae1d93854f95ef1c115aa009113 (diff)
downloadpostgresql-e1caa9040676de4c701294c55c9d819e93ed99cb.tar.gz
Add mention of full text indexing for word searches.
Diffstat (limited to 'doc/FAQ')
-rw-r--r--doc/FAQ9
1 files changed, 3 insertions, 6 deletions
diff --git a/doc/FAQ b/doc/FAQ
index 2ce673620e..015ce4cfe2 100644
--- a/doc/FAQ
+++ b/doc/FAQ
@@ -1,7 +1,7 @@
Frequently Asked Questions (FAQ) for PostgreSQL
- Last updated: Tue Oct 9 16:07:30 EDT 2007
+ Last updated: Tue Oct 9 16:13:00 EDT 2007
Current maintainer: Bruce Momjian (bruce@momjian.us)
@@ -600,12 +600,9 @@
* The default C locale must be used during initdb because it is not
possible to know the next-greatest character in a non-C locale.
You can create a special text_pattern_ops index for such cases
- that work only for LIKE indexing.
+ that work only for LIKE indexing. It is also possible to use full
+ text indexing for word searches.
- 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.
-
4.7) How do I see how the query optimizer is evaluating my query?
See the EXPLAIN manual page.