postgres.git / summary / log / commit / refs

commit    8af71fc56d0103e7bc0ebb12af152ed3b6ab0250
Author:   Tom Lane <tgl@sss.pgh.pa.us>
Date:     Fri Dec 02 16:33:53 2011 +0000
First released in: 9.2.0, 8.4.10, 9.0.7, 9.1.3

    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 318cb554efe..c3a91428033 100644
--- a/doc/src/sgml/libpq.sgml
+++ b/doc/src/sgml/libpq.sgml
@@ -6938,8 +6938,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: 1c635b03c132]