Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
Greenplum
Gpdb
提交
2aac6f10
G
Gpdb
项目概览
Greenplum
/
Gpdb
通知
7
Star
1
Fork
0
代码
文件
提交
分支
Tags
贡献者
分支图
Diff
Issue
0
列表
看板
标记
里程碑
合并请求
0
DevOps
流水线
流水线任务
计划
Wiki
0
Wiki
分析
仓库
DevOps
项目成员
Pages
G
Gpdb
项目概览
项目概览
详情
发布
仓库
仓库
文件
提交
分支
标签
贡献者
分支图
比较
Issue
0
Issue
0
列表
看板
标记
里程碑
合并请求
0
合并请求
0
Pages
DevOps
DevOps
流水线
流水线任务
计划
分析
分析
仓库分析
DevOps
Wiki
0
Wiki
成员
成员
收起侧边栏
关闭侧边栏
动态
分支图
创建新Issue
流水线任务
提交
Issue看板
体验新版 GitCode,发现更多精彩内容 >>
提交
2aac6f10
编写于
10月 27, 2007
作者:
T
Tom Lane
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
Minor wording improvements per suggestion from Jeff Davis. Also tweak
hyphenated-word parser examples per earlier discussion with Alvaro.
上级
8a8bcb44
变更
1
隐藏空白更改
内联
并排
Showing
1 changed file
with
17 addition
and
16 deletion
+17
-16
doc/src/sgml/textsearch.sgml
doc/src/sgml/textsearch.sgml
+17
-16
未找到文件。
doc/src/sgml/textsearch.sgml
浏览文件 @
2aac6f10
<!-- $PostgreSQL: pgsql/doc/src/sgml/textsearch.sgml,v 1.2
6 2007/10/25 13:06:35 alvherre
Exp $ -->
<!-- $PostgreSQL: pgsql/doc/src/sgml/textsearch.sgml,v 1.2
7 2007/10/27 00:19:45 tgl
Exp $ -->
<chapter id="textsearch">
<title id="textsearch-title">Full Text Search</title>
...
...
@@ -1770,7 +1770,7 @@ LIMIT 10;
<row>
<entry><literal>hword</></entry>
<entry>Hyphenated word, all letters</entry>
<entry><literal>
político-militar
</literal></entry>
<entry><literal>
lógico-matemática
</literal></entry>
</row>
<row>
<entry><literal>numhword</></entry>
...
...
@@ -1780,14 +1780,13 @@ LIMIT 10;
<row>
<entry><literal>hword_asciipart</></entry>
<entry>Hyphenated word part, all ASCII</entry>
<entry><literal>militar</literal> in the context
<literal>político-militar</literal>, or <literal>postgresql</literal> in the context <literal>postgresql-beta1</literal></entry>
<entry><literal>postgresql</literal> in the context <literal>postgresql-beta1</literal></entry>
</row>
<row>
<entry><literal>hword_part</></entry>
<entry>Hyphenated word part, all letters</entry>
<entry><literal>
físico</literal> or <literal>químico
</literal>
in the context <literal>
físico-químico
</literal></entry>
<entry><literal>
lógico</literal> or <literal>matemática
</literal>
in the context <literal>
lógico-matemática
</literal></entry>
</row>
<row>
<entry><literal>hword_numpart</></entry>
...
...
@@ -1902,12 +1901,12 @@ SELECT alias, description, token FROM ts_debug('foo-bar-beta1');
instructive example:
<programlisting>
SELECT alias, description, token FROM ts_debug('http://
foo
.com/stuff/index.html');
alias | description |
token
----------+---------------+--------------------------
SELECT alias, description, token FROM ts_debug('http://
example
.com/stuff/index.html');
alias | description |
token
----------+---------------+--------------------------
----
protocol | Protocol head | http://
url | URL |
foo
.com/stuff/index.html
host | Host |
foo
.com
url | URL |
example
.com/stuff/index.html
host | Host |
example
.com
uri | URI | /stuff/index.html
</programlisting>
</para>
...
...
@@ -3093,8 +3092,9 @@ SELECT plainto_tsquery('supernovae stars');
</para>
<para>
A GiST index is <firstterm>lossy</firstterm>, meaning it is necessary
to check the actual table row to eliminate false matches.
A GiST index is <firstterm>lossy</firstterm>, meaning that the index
may produce false matches, and it is necessary
to check the actual table row to eliminate such false matches.
<productname>PostgreSQL</productname> does this automatically; for
example, in the query plan below, the <literal>Filter:</literal>
line indicates the index output will be rechecked:
...
...
@@ -3112,14 +3112,15 @@ EXPLAIN SELECT * FROM apod WHERE textsearch @@ to_tsquery('supernovae');
index by a fixed-length signature. The signature is generated by hashing
each word into a random bit in an n-bit string, with all these bits OR-ed
together to produce an n-bit document signature. When two words hash to
the same bit position there will be a false match
, and i
f all words in
the same bit position there will be a false match
. I
f all words in
the query have matches (real or false) then the table row must be
retrieved to see if the match is correct.
</para>
<para>
Lossiness causes performance degradation since random access to table
records is slow; this limits the usefulness of GiST indexes. The
Lossiness causes performance degradation due to useless fetches of table
records that turn out to be false matches. Since random access to table
records is slow, this limits the usefulness of GiST indexes. The
likelihood of false matches depends on several factors, in particular the
number of unique words, so using dictionaries to reduce this number is
recommended.
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录