Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
P
postgres-lambda-diff
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Jakob Huber
postgres-lambda-diff
Commits
e1caa904
Commit
e1caa904
authored
17 years ago
by
Bruce Momjian
Browse files
Options
Downloads
Patches
Plain Diff
Add mention of full text indexing for word searches.
parent
db962bb1
No related branches found
No related tags found
No related merge requests found
Changes
2
Show whitespace changes
Inline
Side-by-side
Showing
2 changed files
doc/FAQ
+3
-6
3 additions, 6 deletions
doc/FAQ
doc/src/FAQ/FAQ.html
+3
-6
3 additions, 6 deletions
doc/src/FAQ/FAQ.html
with
6 additions
and
12 deletions
doc/FAQ
+
3
−
6
View file @
e1caa904
Frequently Asked Questions (FAQ) for PostgreSQL
Last updated: Tue Oct 9 16:
07:3
0 EDT 2007
Last updated: Tue Oct 9 16:
13:0
0 EDT 2007
Current maintainer: Bruce Momjian (bruce@momjian.us)
...
...
@@ -600,11 +600,8 @@
* 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.
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.
that work only for LIKE indexing. It is also possible to use full
text indexing for word searches.
4.7) How do I see how the query optimizer is evaluating my query?
...
...
This diff is collapsed.
Click to expand it.
doc/src/FAQ/FAQ.html
+
3
−
6
View file @
e1caa904
...
...
@@ -10,7 +10,7 @@
alink=
"#0000ff"
>
<H1>
Frequently Asked Questions (FAQ) for PostgreSQL
</H1>
<P>
Last updated: Tue Oct 9 16:
07:3
0 EDT 2007
</P>
<P>
Last updated: Tue Oct 9 16:
13:0
0 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>
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment