Commite1caa90

committed

Add mention of full text indexing for word searches.

1 parentdb962bb commite1caa90Copy full SHA for e1caa90

File tree

-12

lines changed

-12

lines changed

Lines changed: 3 additions & 6 deletions

Original file line number	Diff line number	Diff line change
`@@ -1,7 +1,7 @@`
`1`	`1`
`2`	`2`	`Frequently Asked Questions (FAQ) for PostgreSQL`
`3`	`3`
`4`		`- Last updated: Tue Oct 9 16:07:30 EDT 2007`
	`4`	`+ Last updated: Tue Oct 9 16:13:00 EDT 2007`
`5`	`5`
`6`	`6`	`Current maintainer: Bruce Momjian (bruce@momjian.us)`
`7`	`7`
`@@ -600,12 +600,9 @@`
`600`	`600`	`* The default C locale must be used during initdb because it is not`
`601`	`601`	`possible to know the next-greatest character in a non-C locale.`
`602`	`602`	`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.`
`604`	`605`
`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`		`-`
`609`	`606`	`4.7) How do I see how the query optimizer is evaluating my query?`
`610`	`607`
`611`	`608`	`See the EXPLAIN manual page.`

Lines changed: 3 additions & 6 deletions

Original file line number	Diff line number	Diff line change
`@@ -10,7 +10,7 @@`
`10`	`10`	`alink="#0000ff">`
`11`	`11`	`<H1>Frequently Asked Questions (FAQ) for PostgreSQL</H1>`
`12`	`12`
`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>`
`14`	`14`
`15`	`15`	`<P>Current maintainer: Bruce Momjian (<Ahref=`
`16`	`16`	`"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`
`784`	`784`	`<i>initdb</i> because it is not possible to know the next-greatest`
`785`	`785`	`character in a non-C locale. You can create a special`
`786`	`786`	`<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.`
`788`	`789`	`</LI>`
`789`	`790`	`</UL>`
`790`	`791`
`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`		`-`
`795`	`792`	`<H3id="item4.7">4.7) How do I see how the query optimizer is`
`796`	`793`	`evaluating my query?</H3>`
`797`	`794`

Comments

(0)