<varlistentry id="libpq-PQsendFlushRequest">
<term><function>PQsendFlushRequest</function><indexterm><primary>PQsendFlushRequest</primary></indexterm></term>
- <listitem>
- <para>
- Sends a request for the server to flush its output buffer.
+ <listitem>
+ <para>
+ Sends a request for the server to flush its output buffer.
<synopsis>
int PQsendFlushRequest(PGconn *conn);
</synopsis>
- </para>
+ </para>
- <para>
- Returns 1 for success. Returns 0 on any failure.
- </para>
- <para>
- The server flushes its output buffer automatically as a result of
- <function>PQpipelineSync</function> being called, or
- on any request when not in pipeline mode; this function is useful
- to cause the server to flush its output buffer in pipeline mode
- without establishing a synchronization point.
- Note that the request is not itself flushed to the server automatically;
- use <function>PQflush</function> if necessary.
- </para>
- </listitem>
- </varlistentry>
+ <para>
+ Returns 1 for success. Returns 0 on any failure.
+ </para>
+ <para>
+ The server flushes its output buffer automatically as a result of
+ <function>PQpipelineSync</function> being called, or
+ on any request when not in pipeline mode; this function is useful
+ to cause the server to flush its output buffer in pipeline mode
+ without establishing a synchronization point.
+ Note that the request is not itself flushed to the server automatically;
+ use <function>PQflush</function> if necessary.
+ </para>
+ </listitem>
+ </varlistentry>
</variablelist>
</sect2>
* error, a PGresult with PGRES_PIPELINE_SYNC is produced.
*
* Queries can already have been sent before PQpipelineSync is called, but
- * PQpipelineSync need to be called before retrieving command results.
+ * PQpipelineSync needs to be called before retrieving command results.
*
* The connection will remain in pipeline mode and unavailable for new
* synchronous command execution functions until all results from the pipeline