Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit1cd1a7c

Browse files
committed
Add some weasel wording about threaded usage of PGresults.
PGresults used to be read-only from the application's viewpoint, but nowthat we've exposed various functions that allow modification of a PGresult,that sweeping statement is no longer accurate. Noted by Dmitriy Igrishin.
1 parentcfd8cf3 commit1cd1a7c

File tree

1 file changed

+6
-2
lines changed

1 file changed

+6
-2
lines changed

‎doc/src/sgml/libpq.sgml

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7161,8 +7161,12 @@ int PQisthreadsafe();
71617161
</para>
71627162

71637163
<para>
7164-
<structname>PGresult</> objects are read-only after creation, and so
7165-
can be passed around freely between threads.
7164+
<structname>PGresult</> objects are normally read-only after creation,
7165+
and so can be passed around freely between threads. However, if you use
7166+
any of the <structname>PGresult</>-modifying functions described in
7167+
<xref linkend="libpq-misc"> or <xref linkend="libpq-events">, it's up
7168+
to you to avoid concurrent operations on the same <structname>PGresult</>,
7169+
too.
71667170
</para>
71677171

71687172
<para>

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp