diff options
Diffstat (limited to 'doc/src')
| -rw-r--r-- | doc/src/sgml/libpq.sgml | 5 | ||||
| -rw-r--r-- | doc/src/sgml/protocol.sgml | 9 |
2 files changed, 8 insertions, 6 deletions
diff --git a/doc/src/sgml/libpq.sgml b/doc/src/sgml/libpq.sgml index e4487cc3223..926a271dc1f 100644 --- a/doc/src/sgml/libpq.sgml +++ b/doc/src/sgml/libpq.sgml @@ -5043,10 +5043,11 @@ int PQflush(PGconn *conn); </para> <para> - While the pipeline API was introduced in + While <application>libpq</application>'s pipeline API was introduced in <productname>PostgreSQL</productname> 14, it is a client-side feature which doesn't require special server support and works on any server - that supports the v3 extended query protocol. + that supports the v3 extended query protocol. For more information see + <xref linkend="protocol-flow-pipelining"/>. </para> <sect2 id="libpq-pipeline-using"> diff --git a/doc/src/sgml/protocol.sgml b/doc/src/sgml/protocol.sgml index 27c55a7c812..0770d278c39 100644 --- a/doc/src/sgml/protocol.sgml +++ b/doc/src/sgml/protocol.sgml @@ -1093,9 +1093,10 @@ SELCT 1/0;<!-- this typo is intentional --> implicit <command>ROLLBACK</command> if they failed. However, there are a few DDL commands (such as <command>CREATE DATABASE</command>) that cannot be executed inside a transaction block. If one of - these is executed in a pipeline, it will, upon success, force an - immediate commit to preserve database consistency. - A Sync immediately following one of these has no effect except to + these is executed in a pipeline, it will fail unless it is the first + command in the pipeline. Furthermore, upon success it will force an + immediate commit to preserve database consistency. Thus a Sync + immediately following one of these commands has no effect except to respond with ReadyForQuery. </para> @@ -1103,7 +1104,7 @@ SELCT 1/0;<!-- this typo is intentional --> When using this method, completion of the pipeline must be determined by counting ReadyForQuery messages and waiting for that to reach the number of Syncs sent. Counting command completion responses is - unreliable, since some of the commands may not be executed and thus not + unreliable, since some of the commands may be skipped and thus not produce a completion message. </para> </sect2> |