{"Entry":{"collection":"psql","key":"cmd-3b","name":"\\;","aliases":["\\;"],"metadata":{"aliases":["\\;"],"category":"Query execution","content_hash":"1e7498fd695ec14e54cf47e0a858741229fce75dd55a6e43e206b051ece98125","derived_content_hash":"d37dd6a247d4d1207dbab7cf888870faf0785d5235f11c647e455f52444465bc","documentation_refresh":{"batch":"20261113","original_source_rev":"","versions":{"14":"14.25","15":"15.20","16":"16.16","17":"17.12","18":"18.7","19":"19rc2"}},"imported_at":"2026-09-30T00:40:44.688256+08:00","name":"\\;","name_zh":"","slug":"cmd-3b","summary":"Backslash-semicolon is not a meta-command in the same way as the preceding commands; rather, it simply causes a semicolon to be added to the query buffer without any further processing."}},"Definition":{"Collection":"psql","Key":"cmd-3b","SourceDatabase":"center","Version":"18","SourceTable":"psql_command","SourceKey":"cmd-3b","SourceRevision":"1b2d62b4845aa46374f2cb680f95d3392322cc8128646992ae4e18d0e7084915","Facts":{"command":"\\;","comparison_data":{"definition":"Backslash-semicolon is not a meta-command in the same way as the preceding commands; rather, it simply causes a semicolon to be added to the query buffer without any further processing. Normally, psql will dispatch an SQL command to the server as soon as it reaches the command-ending semicolon, even if more input remains on the current line. Thus for example entering select 1; select 2; select 3; will result in the three SQL commands being individually sent to the server, with each one's results being displayed before continuing to the next command. However, a semicolon entered as \\; will not trigger command processing, so that the command before it and the one after are effectively combined and sent to the server in one request. So for example select 1\\; select 2\\; select 3; results in sending the three SQL commands to the server in a single request, when the non-backslashed semicolon is reached. The server executes such a request as a single transaction, unless there are explicit BEGIN / COMMIT commands included in the string to divide it into multiple transactions. (See Section 54.2.2.1 for more details about how the server handles multi-query strings.)","modifiers":[],"signature":"\\;","spellings":["\\;"]},"comparison_hash":"0fc4fee885c94dc22930560ccd4d6a126e64692766fdcfcf30a1345393a9a4e9","description":["Backslash-semicolon is not a meta-command in the same way as the preceding commands; rather, it simply causes a semicolon to be added to the query buffer without any further processing."],"description_zh":"反斜线分号不像前面的命令那样是一个元命令；相反，它只是在不进行进一步处理的情况下将一个分号添加到查询缓冲区中。","description_zh_html":"\u003cdd\u003e\u003cp\u003e\n        反斜线分号不像前面的命令那样是一个元命令；相反，它只是在不进行进一步处理的情况下将一个分号添加到查询缓冲区中。\n        \u003c/p\u003e\u003cp\u003e\n        通常，\u003cspan class=\"application\"\u003epsql\u003c/span\u003e 会在到达命令结束的分号时立即将 SQL 命令发送到服务器，即使当前行还有更多输入。因此，例如输入\n\u003c/p\u003e\u003cpre class=\"programlisting\"\u003e\nselect 1; select 2; select 3;\n\u003c/pre\u003e\u003cp\u003e\n        将导致三个 SQL 命令分别发送到服务器，每个命令的结果在继续下一个命令之前显示。然而，输入为\u003ccode class=\"literal\"\u003e\\;\u003c/code\u003e的分号不会触发命令处理，因此它之前和之后的命令实际上被合并并作为一个请求发送到服务器。因此，例如\n\u003c/p\u003e\u003cpre class=\"programlisting\"\u003e\nselect 1\\; select 2\\; select 3;\n\u003c/pre\u003e\u003cp\u003e\n        会在遇到前面没有反斜线的分号时，将这三个 SQL 命令作为单个请求发送到服务器。服务器会将此类请求作为单个事务执行，除非字符串中包含显式的 \u003ccode class=\"command\"\u003eBEGIN\u003c/code\u003e/\u003ccode class=\"command\"\u003eCOMMIT\u003c/code\u003e 命令将其分成多个事务。（有关服务器如何处理多查询字符串的更多详细信息，请参见\u003ca class=\"xref\" href=\"/zh/docs/18/protocol-flow.html#PROTOCOL-FLOW-MULTI-STATEMENT\" title=\"54.2.2.1. 一个简单查询中的多条语句\"\u003e第 54.2.2.1 节\u003c/a\u003e。）\n        \u003c/p\u003e\u003c/dd\u003e","documentation_revision":{"inputs":[{"file":"app-psql.html","kind":"same-version-reviewed-manual","locale":"en","sha256":"af50448485df02bdef2b72b8347192ba029c7082b8d0392ecb17db44ad533aaf","version":"18.7"},{"file":"app-psql.html","kind":"same-version-reviewed-manual","locale":"zh-Hans","sha256":"cb475c53a16d9e06358f5e6c9c5649645db92568cfd319f230c62c9f57ae090b","version":"18.7"}],"release":"18.7","runtime_remeasured":false,"source_revision":"pgdoc:b9f0e7232f60f380d642ac9b99226606c254b552"},"facts":[{"label":"Client","value":"psql 18.7"},{"label":"Case-sensitive spelling","value":"\\;"}],"facts_zh":[{"label":"客户端","value":"psql 18.7"},{"label":"区分大小写的写法","value":"\\;"}],"localization":{"documentation_release":"18.7","language":"en","source_language":"en","source_revision":"pgdoc:b9f0e7232f60f380d642ac9b99226606c254b552","status":"same-version-reviewed-manual"},"manual_html":"\u003cdiv\u003e\u003cdl class=\"variablelist\"\u003e\u003cdt id=\"APP-PSQL-META-COMMAND-SEMICOLON\"\u003e\u003cspan class=\"term\"\u003e\u003ccode class=\"literal\"\u003e\\;\u003c/code\u003e\u003c/span\u003e \u003c/dt\u003e\u003cdd\u003e\u003cp\u003e\n        Backslash-semicolon is not a meta-command in the same way as the\n        preceding commands; rather, it simply causes a semicolon to be\n        added to the query buffer without any further processing.\n        \u003c/p\u003e\u003cp\u003e\n        Normally, \u003cspan class=\"application\"\u003epsql\u003c/span\u003e will dispatch an SQL command to the\n        server as soon as it reaches the command-ending semicolon, even if\n        more input remains on the current line.  Thus for example entering\n\u003c/p\u003e\u003cpre class=\"programlisting\"\u003eselect 1; select 2; select 3;\n\u003c/pre\u003e\u003cp\u003e\n        will result in the three SQL commands being individually sent to\n        the server, with each one's results being displayed before\n        continuing to the next command.  However, a semicolon entered\n        as \u003ccode class=\"literal\"\u003e\\;\u003c/code\u003e will not trigger command processing, so that the\n        command before it and the one after are effectively combined and\n        sent to the server in one request.  So for example\n\u003c/p\u003e\u003cpre class=\"programlisting\"\u003eselect 1\\; select 2\\; select 3;\n\u003c/pre\u003e\u003cp\u003e\n        results in sending the three SQL commands to the server in a single\n        request, when the non-backslashed semicolon is reached.\n        The server executes such a request as a single transaction,\n        unless there are explicit \u003ccode class=\"command\"\u003eBEGIN\u003c/code\u003e/\u003ccode class=\"command\"\u003eCOMMIT\u003c/code\u003e\n        commands included in the string to divide it into multiple\n        transactions.  (See \u003ca class=\"xref\" href=\"/docs/18/protocol-flow.html#PROTOCOL-FLOW-MULTI-STATEMENT\" title=\"54.2.2.1. Multiple Statements in a Simple Query\"\u003eSection 54.2.2.1\u003c/a\u003e\n        for more details about how the server handles multi-query strings.)\n        \u003c/p\u003e\u003c/dd\u003e\u003c/dl\u003e\u003c/div\u003e","manual_path":"app-psql.html#APP-PSQL-META-COMMAND-SEMICOLON","modifiers":[],"related":[{"label":"psql command-line options and complete manual","url":"/wiki/tool/psql/?v=18"}],"related_zh":[{"label":"psql 命令行选项及完整手册","url":"/wiki/tool/psql/?v=18"}],"release":{"channel":"stable","evidence_kind":"English manual and source declarations","label":"18.7","major":"18","manifest":{"major":"18","release":"18.7","source_sha256":"441dfae4280cae3e0425e5f876f80559fb0731c140f1aae22b3e5a54d0411bfd","source_url":"https://ftp.postgresql.org/pub/source/v18.7/postgresql-18.7.tar.bz2"},"ref":"https://ftp.postgresql.org/pub/source/v18.7/postgresql-18.7.tar.bz2","revision":"1b2d62b4845aa46374f2cb680f95d3392322cc8128646992ae4e18d0e7084915","source_sha256":"441dfae4280cae3e0425e5f876f80559fb0731c140f1aae22b3e5a54d0411bfd"},"sections":[],"sections_zh":[],"signature":"\\;","sources":[{"anchor":"APP-PSQL-META-COMMAND-SEMICOLON","file":"app-psql.html","label":"18.7 English manual · app-psql.html","sha256":"af50448485df02bdef2b72b8347192ba029c7082b8d0392ecb17db44ad533aaf","url":"/docs/18/app-psql.html#APP-PSQL-META-COMMAND-SEMICOLON"}],"spellings":["\\;"],"tables":[{"columns":[{"key":"command","label":"Command"},{"key":"modifiers","label":"Documented suffix modifiers"}],"key":"spellings","rows":[{"command":{"text":"\\;","url":"/wiki/psql/cmd-3b/?v=18"},"modifiers":"None listed in this signature"}],"title":"Spellings in this manual definition"}],"tables_zh":[{"columns":[{"key":"command","label":"命令"},{"key":"modifiers","label":"手册中的后缀修饰符"}],"key":"spellings","rows":[{"command":{"text":"\\;","url":"/wiki/psql/cmd-3b/?v=18"},"modifiers":"此语法签名未列出"}],"title":"本版手册中的写法"}],"zh_from":"same-version-manual"},"ManualEvidence":{"manual_path":"app-psql.html#APP-PSQL-META-COMMAND-SEMICOLON","release":{"channel":"stable","evidence_kind":"English manual and source declarations","label":"18.7","major":"18","manifest":{"major":"18","release":"18.7","source_sha256":"441dfae4280cae3e0425e5f876f80559fb0731c140f1aae22b3e5a54d0411bfd","source_url":"https://ftp.postgresql.org/pub/source/v18.7/postgresql-18.7.tar.bz2"},"ref":"https://ftp.postgresql.org/pub/source/v18.7/postgresql-18.7.tar.bz2","revision":"1b2d62b4845aa46374f2cb680f95d3392322cc8128646992ae4e18d0e7084915","source_sha256":"441dfae4280cae3e0425e5f876f80559fb0731c140f1aae22b3e5a54d0411bfd"},"sources":[{"anchor":"APP-PSQL-META-COMMAND-SEMICOLON","file":"app-psql.html","label":"18.7 English manual · app-psql.html","sha256":"af50448485df02bdef2b72b8347192ba029c7082b8d0392ecb17db44ad533aaf","url":"/docs/18/app-psql.html#APP-PSQL-META-COMMAND-SEMICOLON"}]},"MeasuredEvidence":{}},"Text":{"Collection":"psql","Key":"cmd-3b","SourceDatabase":"center","Version":"18","Locale":"en","Title":"\\;","Summary":"Backslash-semicolon is not a meta-command in the same way as the preceding commands; rather, it simply causes a semicolon to be added to the query buffer without any further processing.","BodyHTML":"\u003cdiv\u003e\u003cdl\u003e\u003cdt id=\"APP-PSQL-META-COMMAND-SEMICOLON\"\u003e\u003cspan\u003e\u003ccode\u003e\\;\u003c/code\u003e\u003c/span\u003e \u003c/dt\u003e\u003cdd\u003e\u003cp\u003e\n        Backslash-semicolon is not a meta-command in the same way as the\n        preceding commands; rather, it simply causes a semicolon to be\n        added to the query buffer without any further processing.\n        \u003c/p\u003e\u003cp\u003e\n        Normally, \u003cspan\u003epsql\u003c/span\u003e will dispatch an SQL command to the\n        server as soon as it reaches the command-ending semicolon, even if\n        more input remains on the current line.  Thus for example entering\n\u003c/p\u003e\u003cpre\u003eselect 1; select 2; select 3;\n\u003c/pre\u003e\u003cp\u003e\n        will result in the three SQL commands being individually sent to\n        the server, with each one\u0026#39;s results being displayed before\n        continuing to the next command.  However, a semicolon entered\n        as \u003ccode\u003e\\;\u003c/code\u003e will not trigger command processing, so that the\n        command before it and the one after are effectively combined and\n        sent to the server in one request.  So for example\n\u003c/p\u003e\u003cpre\u003eselect 1\\; select 2\\; select 3;\n\u003c/pre\u003e\u003cp\u003e\n        results in sending the three SQL commands to the server in a single\n        request, when the non-backslashed semicolon is reached.\n        The server executes such a request as a single transaction,\n        unless there are explicit \u003ccode\u003eBEGIN\u003c/code\u003e/\u003ccode\u003eCOMMIT\u003c/code\u003e\n        commands included in the string to divide it into multiple\n        transactions.  (See \u003ca href=\"/docs/18/protocol-flow.html#PROTOCOL-FLOW-MULTI-STATEMENT\" rel=\"nofollow\"\u003eSection 54.2.2.1\u003c/a\u003e\n        for more details about how the server handles multi-query strings.)\n        \u003c/p\u003e\u003c/dd\u003e\u003c/dl\u003e\u003c/div\u003e","SourceRevision":"1b2d62b4845aa46374f2cb680f95d3392322cc8128646992ae4e18d0e7084915","ContentHash":"350deef3bcedc71074a66433d864357d947f8f96c453511186925be56002c8d9","Payload":{"description":["Backslash-semicolon is not a meta-command in the same way as the preceding commands; rather, it simply causes a semicolon to be added to the query buffer without any further processing."],"manual_html":"\u003cdiv\u003e\u003cdl class=\"variablelist\"\u003e\u003cdt id=\"APP-PSQL-META-COMMAND-SEMICOLON\"\u003e\u003cspan class=\"term\"\u003e\u003ccode class=\"literal\"\u003e\\;\u003c/code\u003e\u003c/span\u003e \u003c/dt\u003e\u003cdd\u003e\u003cp\u003e\n        Backslash-semicolon is not a meta-command in the same way as the\n        preceding commands; rather, it simply causes a semicolon to be\n        added to the query buffer without any further processing.\n        \u003c/p\u003e\u003cp\u003e\n        Normally, \u003cspan class=\"application\"\u003epsql\u003c/span\u003e will dispatch an SQL command to the\n        server as soon as it reaches the command-ending semicolon, even if\n        more input remains on the current line.  Thus for example entering\n\u003c/p\u003e\u003cpre class=\"programlisting\"\u003eselect 1; select 2; select 3;\n\u003c/pre\u003e\u003cp\u003e\n        will result in the three SQL commands being individually sent to\n        the server, with each one's results being displayed before\n        continuing to the next command.  However, a semicolon entered\n        as \u003ccode class=\"literal\"\u003e\\;\u003c/code\u003e will not trigger command processing, so that the\n        command before it and the one after are effectively combined and\n        sent to the server in one request.  So for example\n\u003c/p\u003e\u003cpre class=\"programlisting\"\u003eselect 1\\; select 2\\; select 3;\n\u003c/pre\u003e\u003cp\u003e\n        results in sending the three SQL commands to the server in a single\n        request, when the non-backslashed semicolon is reached.\n        The server executes such a request as a single transaction,\n        unless there are explicit \u003ccode class=\"command\"\u003eBEGIN\u003c/code\u003e/\u003ccode class=\"command\"\u003eCOMMIT\u003c/code\u003e\n        commands included in the string to divide it into multiple\n        transactions.  (See \u003ca class=\"xref\" href=\"/docs/18/protocol-flow.html#PROTOCOL-FLOW-MULTI-STATEMENT\" title=\"54.2.2.1. Multiple Statements in a Simple Query\"\u003eSection 54.2.2.1\u003c/a\u003e\n        for more details about how the server handles multi-query strings.)\n        \u003c/p\u003e\u003c/dd\u003e\u003c/dl\u003e\u003c/div\u003e","related":[{"label":"psql command-line options and complete manual","url":"/wiki/tool/psql/?v=18"}],"sections":[],"tables":[{"columns":[{"key":"command","label":"Command"},{"key":"modifiers","label":"Documented suffix modifiers"}],"key":"spellings","rows":[{"command":{"text":"\\;","url":"/wiki/psql/cmd-3b/?v=18"},"modifiers":"None listed in this signature"}],"title":"Spellings in this manual definition"}]}},"RequestedLocale":"en","Fallback":false,"Versions":["11","12","13","14","15","16","17","18","19","20"],"Locales":["en","zh-Hans"],"Signatures":null,"Spellings":[{"Version":"18","Ordinal":0,"Command":"\\;","Signature":"\\;","Modifiers":[]}],"SQLState":null,"Evidence":null}