mirrors/postgres
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Add some weasel wording about threaded usage of PGresults.

Browse Source 
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.
This commit is contained in:
Tom Lane 2011-12-02 11:33:53 -05:00
parent d08b64581f
commit c2e412ad41
1 changed files with 6 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
doc/src/sgml/libpq.sgml
View File

@ -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>