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.

diff --git a/doc/src/sgml/libpq.sgml b/doc/src/sgml/libpq.sgml
index 318cb554efe1a6cbd2622713a28897137de16784..c3a914280334cd5d3371980c071341fbd1dc7795 100644 (file)
--- a/doc/src/sgml/libpq.sgml
+++ b/doc/src/sgml/libpq.sgml
@@ -6938,8 +6938,12 @@ int PQisthreadsafe();
   
 
   
-   PGresult objects are read-only after creation, and so
-   can be passed around freely between threads.
+   PGresult objects are normally read-only after creation,
+   and so can be passed around freely between threads.  However, if you use
+   any of the PGresult-modifying functions described in
+    or , it's up
+   to you to avoid concurrent operations on the same PGresult,
+   too.