Received: from magus.postgresql.org (magus.postgresql.org [87.238.57.229]) by mail.postgresql.org (Postfix) with ESMTP id 7781953F47 for ; Thu, 5 Jan 2012 11:54:09 -0400 (AST) Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1Ripdj-0006PI-7H for pgsql-docs@postgresql.org; Thu, 05 Jan 2012 15:54:09 +0000 Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id q05Frncn015210; Thu, 5 Jan 2012 10:53:49 -0500 (EST) To: Jeff Davis cc: pgsql-docs@postgresql.org Subject: Re: Documentation and mutating PGresult objects In-reply-to: <1325756834.25249.161.camel@jdavis> References: <1325756834.25249.161.camel@jdavis> Comments: In-reply-to Jeff Davis message dated "Thu, 05 Jan 2012 01:47:14 -0800" Date: Thu, 05 Jan 2012 10:53:49 -0500 Message-ID: <15209.1325778829@sss.pgh.pa.us> From: Tom Lane X-Pg-Spam-Score: -1.9 (-) X-Archive-Number: 201201/14 X-Sequence-Number: 7165 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 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