postgres.git / summary / log / commit / refs

commit    1cd1a7c1024503259b3968db6b9e8a888ca97f63
Author:   Tom Lane <tgl@sss.pgh.pa.us>
Date:     Fri Dec 02 16:33:53 2011 +0000

    Add some weasel wording about threaded usage of PGresults.
    
    PGresults used to be read-only from the application's viewpoint, but now
    that we've exposed various functions that allow modification of a PGresult,
    that sweeping statement is no longer accurate.  Noted by Dmitriy Igrishin.


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

diff --git a/doc/src/sgml/libpq.sgml b/doc/src/sgml/libpq.sgml
index 08aa3482637..2ad9a10be23 100644
--- a/doc/src/sgml/libpq.sgml
+++ b/doc/src/sgml/libpq.sgml
@@ -7161,8 +7161,12 @@ int PQisthreadsafe();
   </para>
 
   <para>
-   <structname>PGresult</> objects are read-only after creation, and so
-   can be passed around freely between threads.
+   <structname>PGresult</> objects are normally read-only after creation,
+   and so can be passed around freely between threads.  However, if you use
+   any of the <structname>PGresult</>-modifying functions described in
+   <xref linkend="libpq-misc"> or <xref linkend="libpq-events">, it's up
+   to you to avoid concurrent operations on the same <structname>PGresult</>,
+   too.
   </para>
 
   <para>


[parent: cfd8cf37d20b]