1
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
5
>CREATE TEXT SEARCH PARSER</TITLE
8
CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
10
HREF="mailto:pgsql-docs@postgresql.org"><LINK
12
TITLE="PostgreSQL 9.1beta1 Documentation"
13
HREF="index.html"><LINK
16
HREF="sql-commands.html"><LINK
18
TITLE="CREATE TEXT SEARCH DICTIONARY"
19
HREF="sql-createtsdictionary.html"><LINK
21
TITLE="CREATE TEXT SEARCH TEMPLATE"
22
HREF="sql-createtstemplate.html"><LINK
25
HREF="stylesheet.css"><META
26
HTTP-EQUIV="Content-Type"
27
CONTENT="text/html; charset=ISO-8859-1"><META
29
CONTENT="2011-04-27T21:20:33"></HEAD
35
SUMMARY="Header navigation table"
47
>PostgreSQL 9.1beta1 Documentation</A
56
TITLE="CREATE TEXT SEARCH DICTIONARY"
57
HREF="sql-createtsdictionary.html"
66
TITLE="CREATE TEXT SEARCH DICTIONARY"
67
HREF="sql-createtsdictionary.html"
80
TITLE="CREATE TEXT SEARCH TEMPLATE"
81
HREF="sql-createtstemplate.html"
89
TITLE="CREATE TEXT SEARCH TEMPLATE"
90
HREF="sql-createtstemplate.html"
101
NAME="SQL-CREATETSPARSER"
103
>CREATE TEXT SEARCH PARSER</H1
111
>CREATE TEXT SEARCH PARSER -- define a new text search parser</DIV
113
CLASS="REFSYNOPSISDIV"
121
>CREATE TEXT SEARCH PARSER <TT
136
>gettoken_function</I
148
>lextypes_function</I
154
>headline_function</I
169
>CREATE TEXT SEARCH PARSER</TT
170
> creates a new text search
171
parser. A text search parser defines a method for splitting a text
172
string into tokens and assigning types (categories) to the tokens.
173
A parser is not particularly useful by itself, but must be bound into a
174
text search configuration along with some text search dictionaries
175
to be used for searching.
178
> If a schema name is given then the text search parser is created in the
179
specified schema. Otherwise it is created in the current schema.
182
> You must be a superuser to use <TT
184
>CREATE TEXT SEARCH PARSER</TT
186
(This restriction is made because an erroneous text search parser
187
definition could confuse or even crash the server.)
191
HREF="textsearch.html"
193
> for further information.
217
> The name of the text search parser to be created. The name can be
230
> The name of the start function for the parser.
237
>gettoken_function</I
242
> The name of the get-next-token function for the parser.
254
> The name of the end function for the parser.
261
>lextypes_function</I
266
> The name of the lextypes function for the parser (a function that
267
returns information about the set of token types it produces).
274
>headline_function</I
279
> The name of the headline function for the parser (a function that
280
summarizes a set of tokens).
286
> The function names can be schema-qualified if necessary. Argument types
287
are not given, since the argument list for each type of function is
288
predetermined. All except the headline function are required.
291
> The arguments can appear in any order, not only the one shown above.
305
>CREATE TEXT SEARCH PARSER</TT
306
> statement in the SQL
318
HREF="sql-altertsparser.html"
319
>ALTER TEXT SEARCH PARSER</A
321
HREF="sql-droptsparser.html"
322
>DROP TEXT SEARCH PARSER</A
329
SUMMARY="Footer navigation table"
340
HREF="sql-createtsdictionary.html"
358
HREF="sql-createtstemplate.html"
368
>CREATE TEXT SEARCH DICTIONARY</TD
374
HREF="sql-commands.html"
382
>CREATE TEXT SEARCH TEMPLATE</TD
b'\\ No newline at end of file'