Received: from magus.postgresql.org (magus.postgresql.org [87.238.57.229]) by mail.postgresql.org (Postfix) with ESMTP id 68B42DDBC2B for ; Fri, 2 Dec 2011 12:37:26 -0400 (AST) Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1RWW72-0007tt-7O for pgsql-docs@postgresql.org; Fri, 02 Dec 2011 16:37:26 +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 pB2GbAFD018799; Fri, 2 Dec 2011 11:37:10 -0500 (EST) To: Dmitriy Igrishin cc: pgsql-docs Subject: Re: Misinformation in 31.18 chapter. In-reply-to: References: Comments: In-reply-to Dmitriy Igrishin message dated "Fri, 02 Dec 2011 12:15:58 +0300" Date: Fri, 02 Dec 2011 11:37:10 -0500 Message-ID: <18798.1322843830@sss.pgh.pa.us> From: Tom Lane X-Pg-Spam-Score: -3.1 (---) X-Archive-Number: 201112/3 X-Sequence-Number: 7110 Dmitriy Igrishin writes: > According to 31.18, > http://www.postgresql.org/docs/9.1/static/libpq-threading.html > "PGresult objects are read-only after creation, and so can be passed around > freely between threads." > But PGresult objects are *not* read-only because of existence of > PQsetvalue() described in > http://www.postgresql.org/docs/9.1/static/libpq-misc.html Good point ... and the "event" stuff can modify the state of a PGresult, too. I've updated that statement accordingly. Thanks for the note. regards, tom lane