From: PG Doc comments form <noreply@postgresql.org>
To: pgsql-docs@lists.postgresql.org
Cc: jbe-mlist@magnetkern.de
Subject: Non-blocking synchronization in libpq using pipeline mode
Date: Wed, 06 Mar 2024 23:42:15 +0000
Message-ID: <170976853548.643.17571475764668611072@wrigleys.postgresql.org> (raw)
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/16/libpq-pipeline-mode.html
Description:
The calls to PQpipelineSync and PQsendFlushRequest may either report failure
or success, but not that data could not be written as of yet because the
request would block.
Does this mean that
1. these functions will always block when invoked and the socket is not
ready to accept the number of bytes that need to be written (assuming the
number of bytes required to be written is greater than one byte)
or
2. the synchronization or flush request need to be flushed manually with
successive PQflush calls
or
3. the functions will return an error condition when the connection is
non-blocking and no data could be written.
Any clarification in the documentation would be appreciated.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: noreply@postgresql.org, pgsql-docs@lists.postgresql.org, jbe-mlist@magnetkern.de
Subject: Re: Non-blocking synchronization in libpq using pipeline mode
In-Reply-To: <170976853548.643.17571475764668611072@wrigleys.postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox