diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2011-12-02 11:33:53 -0500 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2011-12-02 11:34:14 -0500 |
| commit | 1cd1a7c1024503259b3968db6b9e8a888ca97f63 (patch) | |
| tree | a97f9e587c80555a2400d2e030ba9e5ac1fec65c | |
| parent | cfd8cf37d20be715e4bb9e382844c79556516824 (diff) | |
| download | postgresql-1cd1a7c1024503259b3968db6b9e8a888ca97f63.tar.gz | |
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.
| -rw-r--r-- | doc/src/sgml/libpq.sgml | 8 |
1 files changed, 6 insertions, 2 deletions
diff --git a/doc/src/sgml/libpq.sgml b/doc/src/sgml/libpq.sgml index 08aa348263..2ad9a10be2 100644 --- a/doc/src/sgml/libpq.sgml +++ b/doc/src/sgml/libpq.sgml @@ -7161,8 +7161,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> |