Re: Documentation and mutating PGresult objects

From: Dmitriy Igrishin <dmitigr(at)gmail(dot)com>
To: Jeff Davis <pgsql(at)j-davis(dot)com>
Cc: pgsql-docs(at)postgresql(dot)org
Subject: Re: Documentation and mutating PGresult objects
Date: 2012-01-05 15:47:57
Message-ID: CAAfz9KMqy1ENE_Eq4Oi0av2Hy+qyP3RjdWhCqNf+w1+Z7OQUWQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

Hey Jeff,

2012/1/5 Jeff Davis <pgsql(at)j-davis(dot)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.

In response to

Browse pgsql-docs by date

  From Date Subject
Next Message Tom Lane 2012-01-05 15:53:49 Re: Documentation and mutating PGresult objects
Previous Message Jeff Davis 2012-01-05 09:47:14 Documentation and mutating PGresult objects