postgres.git / summary / log / commit / refs

commit    fe88b2043a232b71bb5727e9f026393fb77fb0ed
Author:   Tom Lane <tgl@sss.pgh.pa.us>
Date:     Thu Jun 09 19:08:47 2005 +0000
First released in: 8.1.0, 7.4.9, 8.0.4

    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 1242b324c39..3e874fbb3ed 100644
--- a/doc/src/sgml/libpq.sgml
+++ b/doc/src/sgml/libpq.sgml
@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/libpq.sgml,v 1.141.2.1 2003/11/12 20:05:14 petere Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/libpq.sgml,v 1.141.2.2 2005/06/09 19:08:47 tgl Exp $
 -->
 
  <chapter id="libpq">
@@ -2917,8 +2917,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>


[parent: 39c939895622]