Re: Misinformation in 31.18 chapter.

Lists: pgsql-docs
From: Dmitriy Igrishin <dmitigr(at)gmail(dot)com>
To: pgsql-docs <pgsql-docs(at)postgresql(dot)org>
Subject: Misinformation in 31.18 chapter.
Date: 2011-12-02 09:15:58
Message-ID: CAAfz9KNYSS2EeY2RzDUwkd+yb0kk6sD5PM3yHFdyn5b8hK-uWQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-docs

Hey,

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

--
// Dmitriy.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Dmitriy Igrishin <dmitigr(at)gmail(dot)com>
Cc: pgsql-docs <pgsql-docs(at)postgresql(dot)org>
Subject: Re: Misinformation in 31.18 chapter.
Date: 2011-12-02 16:37:10
Message-ID: 18798.1322843830@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-docs

Dmitriy Igrishin <dmitigr(at)gmail(dot)com> 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