From 0b8e46e49b6236b64744659afe43a74c46042951 Mon Sep 17 00:00:00 2001
From: Tom Lane <tgl@sss.pgh.pa.us>
Date: Thu, 9 Jun 2005 19:08:28 +0000
Subject: [PATCH] Repair error in description of nonblocking usage of
 PQgetCopyData(). Per Volkan Yazici.

---
 doc/src/sgml/libpq.sgml | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/doc/src/sgml/libpq.sgml b/doc/src/sgml/libpq.sgml
index 8430a12429..adee93a885 100644
--- a/doc/src/sgml/libpq.sgml
+++ b/doc/src/sgml/libpq.sgml
@@ -1,5 +1,5 @@
 <!--
-$PostgreSQL: pgsql/doc/src/sgml/libpq.sgml,v 1.182 2005/06/04 20:42:41 momjian Exp $
+$PostgreSQL: pgsql/doc/src/sgml/libpq.sgml,v 1.183 2005/06/09 19:08:28 tgl Exp $
 -->
 
  <chapter id="libpq">
@@ -3230,8 +3230,8 @@ A result of -2 indicates that an error occurred (consult
 When <parameter>async</> is true (not zero), <function>PQgetCopyData</>
 will not block waiting for input; it will return zero if the <command>COPY</command> is still
 in progress but no complete row is available.  (In this case wait for
-read-ready before trying again; it does not matter whether you call
-<function>PQconsumeInput</>.)  When <parameter>async</> is
+read-ready and then call <function>PQconsumeInput</> before calling
+<function>PQgetCopyData</> again.)  When <parameter>async</> is
 false (zero), <function>PQgetCopyData</> will block until data is available
 or the operation completes.
 </para>
-- 
2.40.0