{"Entry":{"collection":"psql","key":"cmd-3b","name":"\\;","aliases":["\\;"],"metadata":{"aliases":["\\;"],"category":"Query execution","content_hash":"1e7498fd695ec14e54cf47e0a858741229fce75dd55a6e43e206b051ece98125","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":"ee8d1a3612338fd9adf250730cb640fcc5233b5491337cc00a316a44e3a0b9f8","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."],"facts":[{"label":"Client","value":"psql 18.6"},{"label":"Case-sensitive spelling","value":"\\;"}],"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\n\u003cp\u003eBackslash-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.\u003c/p\u003e\n\u003cp\u003eNormally, \u003cspan class=\"application\"\u003epsql\u003c/span\u003e 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\u003c/p\u003e\n\u003cpre class=\"programlisting\"\u003eselect 1; select 2; select 3;\n\u003c/pre\u003e\n\u003cp\u003ewill 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 \u003ccode class=\"literal\"\u003e\\;\u003c/code\u003e 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\u003c/p\u003e\n\u003cpre class=\"programlisting\"\u003eselect 1\\; select 2\\; select 3;\n\u003c/pre\u003e\n\u003cp\u003eresults 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 \u003ccode class=\"command\"\u003eBEGIN\u003c/code\u003e/\u003ccode class=\"command\"\u003eCOMMIT\u003c/code\u003e commands included in the string to divide it into multiple 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 for more details about how the server handles multi-query strings.)\u003c/p\u003e\n\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"}],"release":{"channel":"stable","evidence_kind":"English manual and source declarations","label":"18.6","major":"18","manifest":{"index":"index.html","major":"18","pages":1148,"pdf":{"A4":{"built_at":"2026-09-26","bytes":15865106,"pages":3154,"sha256":"19512c405da53f9f7fcf0abba359223aa65f021be025bf3411381918f92e3190","url":"/files/documentation/pdf/18/postgresql-18-A4.pdf"},"US":{"built_at":"2026-09-26","bytes":15748059,"pages":3328,"sha256":"facbe6c229e598b872d3d98bef53308f46e06746006fa4590de9a7de9dd46319","url":"/files/documentation/pdf/18/postgresql-18-US.pdf"}},"release":"18.6","source_mode":"en SGML built with pinned official archive","source_sha256":"555610c24d53e4316da5b7d3fc25c279d96856d5e0e23ee308c328c5fa881d9f","source_url":"https://ftp.postgresql.org/pub/source/v18.6/postgresql-18.6.tar.bz2","svg_assets":3,"tree":"18"},"ref":"https://ftp.postgresql.org/pub/source/v18.6/postgresql-18.6.tar.bz2","revision":"ee8d1a3612338fd9adf250730cb640fcc5233b5491337cc00a316a44e3a0b9f8","source_sha256":"555610c24d53e4316da5b7d3fc25c279d96856d5e0e23ee308c328c5fa881d9f"},"sections":[],"signature":"\\;","sources":[{"anchor":"APP-PSQL-META-COMMAND-SEMICOLON","file":"app-psql.html","label":"18.6 English manual · app-psql.html","sha256":"fa2a1d39294b8854318e82e93f71272c645ed88150ecc2786c28902c3f32782c","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"}]},"ManualEvidence":{"manual_path":"app-psql.html#APP-PSQL-META-COMMAND-SEMICOLON","release":{"channel":"stable","evidence_kind":"English manual and source declarations","label":"18.6","major":"18","manifest":{"index":"index.html","major":"18","pages":1148,"pdf":{"A4":{"built_at":"2026-09-26","bytes":15865106,"pages":3154,"sha256":"19512c405da53f9f7fcf0abba359223aa65f021be025bf3411381918f92e3190","url":"/files/documentation/pdf/18/postgresql-18-A4.pdf"},"US":{"built_at":"2026-09-26","bytes":15748059,"pages":3328,"sha256":"facbe6c229e598b872d3d98bef53308f46e06746006fa4590de9a7de9dd46319","url":"/files/documentation/pdf/18/postgresql-18-US.pdf"}},"release":"18.6","source_mode":"en SGML built with pinned official archive","source_sha256":"555610c24d53e4316da5b7d3fc25c279d96856d5e0e23ee308c328c5fa881d9f","source_url":"https://ftp.postgresql.org/pub/source/v18.6/postgresql-18.6.tar.bz2","svg_assets":3,"tree":"18"},"ref":"https://ftp.postgresql.org/pub/source/v18.6/postgresql-18.6.tar.bz2","revision":"ee8d1a3612338fd9adf250730cb640fcc5233b5491337cc00a316a44e3a0b9f8","source_sha256":"555610c24d53e4316da5b7d3fc25c279d96856d5e0e23ee308c328c5fa881d9f"},"sources":[{"anchor":"APP-PSQL-META-COMMAND-SEMICOLON","file":"app-psql.html","label":"18.6 English manual · app-psql.html","sha256":"fa2a1d39294b8854318e82e93f71272c645ed88150ecc2786c28902c3f32782c","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\n\u003cp\u003eBackslash-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.\u003c/p\u003e\n\u003cp\u003eNormally, \u003cspan\u003epsql\u003c/span\u003e 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\u003c/p\u003e\n\u003cpre\u003eselect 1; select 2; select 3;\n\u003c/pre\u003e\n\u003cp\u003ewill result in the three SQL commands being individually sent to the server, with each one\u0026#39;s results being displayed before continuing to the next command. However, a semicolon entered as \u003ccode\u003e\\;\u003c/code\u003e 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\u003c/p\u003e\n\u003cpre\u003eselect 1\\; select 2\\; select 3;\n\u003c/pre\u003e\n\u003cp\u003eresults 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 \u003ccode\u003eBEGIN\u003c/code\u003e/\u003ccode\u003eCOMMIT\u003c/code\u003e commands included in the string to divide it into multiple transactions. (See \u003ca href=\"/docs/18/protocol-flow.html#PROTOCOL-FLOW-MULTI-STATEMENT\" rel=\"nofollow\"\u003eSection 54.2.2.1\u003c/a\u003e for more details about how the server handles multi-query strings.)\u003c/p\u003e\n\u003c/dd\u003e\u003c/dl\u003e\u003c/div\u003e","SourceRevision":"ee8d1a3612338fd9adf250730cb640fcc5233b5491337cc00a316a44e3a0b9f8","ContentHash":"9ae5798621b8fd2fca0c0a8afd0c9607b6e9093109b3f42c55fa34497dfdda56","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\n\u003cp\u003eBackslash-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.\u003c/p\u003e\n\u003cp\u003eNormally, \u003cspan class=\"application\"\u003epsql\u003c/span\u003e 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\u003c/p\u003e\n\u003cpre class=\"programlisting\"\u003eselect 1; select 2; select 3;\n\u003c/pre\u003e\n\u003cp\u003ewill 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 \u003ccode class=\"literal\"\u003e\\;\u003c/code\u003e 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\u003c/p\u003e\n\u003cpre class=\"programlisting\"\u003eselect 1\\; select 2\\; select 3;\n\u003c/pre\u003e\n\u003cp\u003eresults 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 \u003ccode class=\"command\"\u003eBEGIN\u003c/code\u003e/\u003ccode class=\"command\"\u003eCOMMIT\u003c/code\u003e commands included in the string to divide it into multiple 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 for more details about how the server handles multi-query strings.)\u003c/p\u003e\n\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":"zh-Hans","Fallback":true,"Versions":["11","12","13","14","15","16","17","18","19","20"],"Locales":["en"],"Signatures":null,"Spellings":[{"Version":"18","Ordinal":0,"Command":"\\;","Signature":"\\;","Modifiers":[]}],"SQLState":null,"Evidence":null}