From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jeff Davis <pgsql@j-davis.com>
Cc: pgsql-docs@postgresql.org
Subject: Re: Documentation and mutating PGresult objects
Date: Thu, 05 Jan 2012 10:53:49 -0500
Message-ID: <15209.1325778829@sss.pgh.pa.us> (raw)
In-Reply-To: <1325756834.25249.161.camel@jdavis>
References: <1325756834.25249.161.camel@jdavis>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: tgl@sss.pgh.pa.us, pgsql@j-davis.com
Subject: Re: Documentation and mutating PGresult objects
In-Reply-To: <15209.1325778829@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
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