summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--doc/src/sgml/libpq.sgml8
1 files changed, 6 insertions, 2 deletions
diff --git a/doc/src/sgml/libpq.sgml b/doc/src/sgml/libpq.sgml
index 702ad888f5e..04f0a5876e3 100644
--- a/doc/src/sgml/libpq.sgml
+++ b/doc/src/sgml/libpq.sgml
@@ -6607,8 +6607,12 @@ myEventProc(PGEventId evtId, void *evtInfo, void *passThrough)
</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>