create_text_search_parser(7)

NAME#

CREATE_TEXT_SEARCH_PARSER - define a new text search parser

SYNOPSIS#

CREATE TEXT SEARCH PARSER \nname\n (
\n
    START = \nstart_function\n ,
\n
    GETTOKEN = \ngettoken_function\n ,
\n
    END = \nend_function\n ,
\n
    LEXTYPES = \nlextypes_function\n
\n
    [, HEADLINE = \nheadline_function\n ]
)

DESCRIPTION#

CREATE TEXT SEARCH PARSER creates a new text search parser. A text search parser defines a method for splitting a text string into tokens and assigning types (categories) to the tokens. A parser is not particularly useful by itself, but must be bound into a text search configuration along with some text search dictionaries to be used for searching.

If a schema name is given then the text search parser is created in the specified schema. Otherwise it is created in the current schema.

You must be a superuser to use CREATE TEXT SEARCH PARSER. (This restriction is made because an erroneous text search parser definition could confuse or even crash the server.)

Refer to Chapter 12 for further information.

PARAMETERS#

name

start_function

gettoken_function

end_function

lextypes_function

headline_function

The function names can be schema-qualified if necessary. Argument types are not given, since the argument list for each type of function is predetermined. All except the headline function are required.

The arguments can appear in any order, not only the one shown above.

COMPATIBILITY#

There is no CREATE TEXT SEARCH PARSER statement in the SQL standard.

SEE ALSO#

ALTER TEXT SEARCH PARSER (ALTER_TEXT_SEARCH_PARSER(7)), DROP TEXT SEARCH PARSER (DROP_TEXT_SEARCH_PARSER(7))