Received: from makus.postgresql.org (makus.postgresql.org [98.129.198.125]) by mail.postgresql.org (Postfix) with ESMTP id 31F4053F45 for ; Thu, 5 Jan 2012 05:46:42 -0400 (AST) Received: from mail-iy0-f174.google.com ([209.85.210.174]) by makus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1RijuA-0005WE-N1 for pgsql-docs@postgresql.org; Thu, 05 Jan 2012 09:46:42 +0000 Received: by iaeh11 with SMTP id h11so674635iae.19 for ; Thu, 05 Jan 2012 01:46:26 -0800 (PST) Received: by 10.50.168.2 with SMTP id zs2mr1556335igb.21.1325756785981; Thu, 05 Jan 2012 01:46:25 -0800 (PST) Received: from [192.168.1.102] (c-69-181-249-16.hsd1.ca.comcast.net. [69.181.249.16]) by mx.google.com with ESMTPS id t5sm111332662igb.4.2012.01.05.01.46.24 (version=SSLv3 cipher=OTHER); Thu, 05 Jan 2012 01:46:24 -0800 (PST) Message-ID: <1325756834.25249.161.camel@jdavis> Subject: Documentation and mutating PGresult objects From: Jeff Davis To: pgsql-docs@postgresql.org Date: Thu, 05 Jan 2012 01:47:14 -0800 Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.2.1- Content-Transfer-Encoding: 7bit Mime-Version: 1.0 X-Pg-Spam-Score: -2.6 (--) X-Archive-Number: 201201/12 X-Sequence-Number: 7163 "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