{
    "content": [
        {
            "type": "text",
            "text": "# CREATE_TEXT_SEARCH_PARSER (man)\n\n## NAME\n\nCREATETEXTSEARCHPARSER - define a new text search parser\n\n## SYNOPSIS\n\nCREATE TEXT SEARCH PARSER name (\nSTART = startfunction ,\nGETTOKEN = gettokenfunction ,\nEND = endfunction ,\nLEXTYPES = lextypesfunction\n[, HEADLINE = headlinefunction ]\n)\n\n## DESCRIPTION\n\nCREATE TEXT SEARCH PARSER creates a new text search parser. A text search parser defines a\nmethod for splitting a text string into tokens and assigning types (categories) to the\ntokens. A parser is not particularly useful by itself, but must be bound into a text search\nconfiguration along with some text search dictionaries to be used for searching.\n\n## Sections\n\n- **NAME**\n- **SYNOPSIS**\n- **DESCRIPTION**\n- **PARAMETERS**\n- **COMPATIBILITY**\n- **SEE ALSO**\n\nUse structuredContent.sections for detailed options, examples, and full documentation.\n"
        }
    ],
    "structuredContent": {
        "command": "CREATE_TEXT_SEARCH_PARSER",
        "section": "",
        "mode": "man",
        "summary": "CREATETEXTSEARCHPARSER - define a new text search parser",
        "synopsis": "CREATE TEXT SEARCH PARSER name (\nSTART = startfunction ,\nGETTOKEN = gettokenfunction ,\nEND = endfunction ,\nLEXTYPES = lextypesfunction\n[, HEADLINE = headlinefunction ]\n)",
        "tldr_summary": null,
        "tldr_examples": [],
        "tldr_source": null,
        "flags": [],
        "examples": [],
        "see_also": [
            {
                "name": "ALTERTEXTSEARCHPARSER",
                "section": "7",
                "url": "https://www.chedong.com/phpMan.php/man/ALTERTEXTSEARCHPARSER/7/json"
            },
            {
                "name": "DROPTEXTSEARCHPARSER",
                "section": "7",
                "url": "https://www.chedong.com/phpMan.php/man/DROPTEXTSEARCHPARSER/7/json"
            },
            {
                "name": "PARSER",
                "section": "7",
                "url": "https://www.chedong.com/phpMan.php/man/PARSER/7/json"
            }
        ],
        "section_outline": [
            {
                "name": "NAME",
                "lines": 2,
                "subsections": []
            },
            {
                "name": "SYNOPSIS",
                "lines": 8,
                "subsections": []
            },
            {
                "name": "DESCRIPTION",
                "lines": 13,
                "subsections": []
            },
            {
                "name": "PARAMETERS",
                "lines": 26,
                "subsections": []
            },
            {
                "name": "COMPATIBILITY",
                "lines": 2,
                "subsections": []
            },
            {
                "name": "SEE ALSO",
                "lines": 6,
                "subsections": []
            }
        ],
        "sections": {
            "NAME": {
                "content": "CREATETEXTSEARCHPARSER - define a new text search parser\n",
                "subsections": []
            },
            "SYNOPSIS": {
                "content": "CREATE TEXT SEARCH PARSER name (\nSTART = startfunction ,\nGETTOKEN = gettokenfunction ,\nEND = endfunction ,\nLEXTYPES = lextypesfunction\n[, HEADLINE = headlinefunction ]\n)\n",
                "subsections": []
            },
            "DESCRIPTION": {
                "content": "CREATE TEXT SEARCH PARSER creates a new text search parser. A text search parser defines a\nmethod for splitting a text string into tokens and assigning types (categories) to the\ntokens. A parser is not particularly useful by itself, but must be bound into a text search\nconfiguration along with some text search dictionaries to be used for searching.\n\nIf a schema name is given then the text search parser is created in the specified schema.\nOtherwise it is created in the current schema.\n\nYou must be a superuser to use CREATE TEXT SEARCH PARSER. (This restriction is made because\nan erroneous text search parser definition could confuse or even crash the server.)\n\nRefer to Chapter 12 for further information.\n",
                "subsections": []
            },
            "PARAMETERS": {
                "content": "name\nThe name of the text search parser to be created. The name can be schema-qualified.\n\nstartfunction\nThe name of the start function for the parser.\n\ngettokenfunction\nThe name of the get-next-token function for the parser.\n\nendfunction\nThe name of the end function for the parser.\n\nlextypesfunction\nThe name of the lextypes function for the parser (a function that returns information\nabout the set of token types it produces).\n\nheadlinefunction\nThe name of the headline function for the parser (a function that summarizes a set of\ntokens).\n\nThe function names can be schema-qualified if necessary. Argument types are not given, since\nthe argument list for each type of function is predetermined. All except the headline\nfunction are required.\n\nThe arguments can appear in any order, not only the one shown above.\n",
                "subsections": []
            },
            "COMPATIBILITY": {
                "content": "There is no CREATE TEXT SEARCH PARSER statement in the SQL standard.\n",
                "subsections": []
            },
            "SEE ALSO": {
                "content": "ALTER TEXT SEARCH PARSER (ALTERTEXTSEARCHPARSER(7)), DROP TEXT SEARCH PARSER\n(DROPTEXTSEARCHPARSER(7))\n\n\n\nPostgreSQL 14.23                                2026                    CREATE TEXT SEARCH PARSER(7)",
                "subsections": []
            }
        }
    }
}