mirror of
https://git.postgresql.org/git/postgresql.git
synced 2024-12-15 08:20:16 +08:00
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.
This commit is contained in:
parent
1c635b03c1
commit
8af71fc56d
@ -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>
|
||||
|
Loading…
Reference in New Issue
Block a user