pg.ddx.io pgsql-docs@postgresql.org mailing list archive
help / color / mirror / Atom feedDocumentation and mutating PGresult objects
3+ messages / 3 participants
[nested] [flat]
* Documentation and mutating PGresult objects
@ 2012-01-05 09:47 Jeff Davis <pgsql@j-davis.com>
2012-01-05 15:47 ` Re: Documentation and mutating PGresult objects Dmitriy Igrishin <dmitigr@gmail.com>
2012-01-05 15:53 ` Re: Documentation and mutating PGresult objects Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 2 replies; 3+ messages in thread
From: Jeff Davis @ 2012-01-05 09:47 UTC (permalink / raw)
To: pgsql-docs
"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 well as
connection objects?
Regards,
Jeff Davis
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Documentation and mutating PGresult objects
2012-01-05 09:47 Documentation and mutating PGresult objects Jeff Davis <pgsql@j-davis.com>
@ 2012-01-05 15:47 ` Dmitriy Igrishin <dmitigr@gmail.com>
1 sibling, 0 replies; 3+ messages in thread
From: Dmitriy Igrishin @ 2012-01-05 15:47 UTC (permalink / raw)
To: Jeff Davis <pgsql@j-davis.com>; +Cc: pgsql-docs
Hey Jeff,
2012/1/5 Jeff Davis <pgsql@j-davis.com>
> "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 well as
> connection objects?
>
> Fixed a month ago:
http://archives.postgresql.org/pgsql-docs/2011-12/msg00002.php
--
// Dmitriy.
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Documentation and mutating PGresult objects
2012-01-05 09:47 Documentation and mutating PGresult objects Jeff Davis <pgsql@j-davis.com>
@ 2012-01-05 15:53 ` Tom Lane <tgl@sss.pgh.pa.us>
1 sibling, 0 replies; 3+ messages in thread
From: Tom Lane @ 2012-01-05 15:53 UTC (permalink / raw)
To: Jeff Davis <pgsql@j-davis.com>; +Cc: pgsql-docs
Jeff Davis <pgsql@j-davis.com> 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 <tgl@sss.pgh.pa.us>
Branch: master [0de93a9c6] 2011-12-02 11:33:53 -0500
Branch: REL9_1_STABLE [1cd1a7c10] 2011-12-02 11:34:14 -0500
Branch: REL9_0_STABLE [8af71fc56] 2011-12-02 11:34:20 -0500
Branch: REL8_4_STABLE Release: REL8_4_10 [c2e412ad4] 2011-12-02 11:34:26 -0500
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.
regards, tom lane
^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2012-01-05 15:53 UTC | newest]
Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2012-01-05 09:47 Documentation and mutating PGresult objects Jeff Davis <pgsql@j-davis.com>
2012-01-05 15:47 ` Dmitriy Igrishin <dmitigr@gmail.com>
2012-01-05 15:53 ` Tom Lane <tgl@sss.pgh.pa.us>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox