From e75d99818dd3940be997520e64db8c9e3b207e39 Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Tue, 21 May 2024 07:05:26 +0200 Subject: Merging upstream version 15.7. Signed-off-by: Daniel Baumann --- doc/src/sgml/html/libpq-async.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'doc/src/sgml/html/libpq-async.html') diff --git a/doc/src/sgml/html/libpq-async.html b/doc/src/sgml/html/libpq-async.html index f27443f..4087c8b 100644 --- a/doc/src/sgml/html/libpq-async.html +++ b/doc/src/sgml/html/libpq-async.html @@ -1,5 +1,5 @@ -34.4. Asynchronous Command Processing
34.4. Asynchronous Command Processing
Prev UpChapter 34. libpq — C LibraryHome Next

34.4. Asynchronous Command Processing

+34.4. Asynchronous Command Processing

34.4. Asynchronous Command Processing
Prev UpChapter 34. libpq — C LibraryHome Next

34.4. Asynchronous Command Processing

The PQexec function is adequate for submitting commands in normal, synchronous applications. It has a few deficiencies, however, that can be of importance to some users: @@ -335,4 +335,4 @@ int PQflush(PGconn *conn); messages, and won't read our data until we read its.) Once PQflush returns 0, wait for the socket to be read-ready and then read the response as described above. -

Prev Up Next
34.3. Command Execution Functions Home 34.5. Pipeline Mode
\ No newline at end of file +

Prev Up Next
34.3. Command Execution Functions Home 34.5. Pipeline Mode
\ No newline at end of file -- cgit v1.2.3