Re: [DOCS] Documentation and mutating PGresult objects

2012-01-05 Thread Tom Lane
Jeff Davis writes: > "PGresult objects are read-only after creation, and so can be passed > around freely between threads." > From http://www.postgresql.org/docs/9.1/static/libpq-threading.html That's not what it says now. Author: Tom Lane Branch: master [0de93a9c6] 2011-12-02 11:33:53 -0500 Br

Re: [DOCS] Documentation and mutating PGresult objects

2012-01-05 Thread Dmitriy Igrishin
Hey Jeff, 2012/1/5 Jeff Davis > "PGresult objects are read-only after creation, and so can be passed > around freely between threads." > > From http://www.postgresql.org/docs/9.1/static/libpq-threading.html > > But what about things like PQsetvalue? Is that a documentation bug? > Should result o

[DOCS] Documentation and mutating PGresult objects

2012-01-05 Thread Jeff Davis
"PGresult objects are read-only after creation, and so can be passed around freely between threads." >From http://www.postgresql.org/docs/9.1/static/libpq-threading.html But what about things like PQsetvalue? Is that a documentation bug? Should result objects be protected by synchronization as we