mirror of
https://git.postgresql.org/git/postgresql.git
synced 2025-03-01 19:45:33 +08:00
Fix docs to not claim ECPG's SET CONNECTION is not thread-aware.
Changed by: Tsunakawa, Takayuki <tsunakawa.takay@jp.fujitsu.com>
This commit is contained in:
parent
f2fa0c6514
commit
9d1758d1e6
@ -238,8 +238,7 @@ EXEC SQL AT <replaceable>connection-name</replaceable> SELECT ...;
|
||||
<para>
|
||||
If your application uses multiple threads of execution, they cannot share a
|
||||
connection concurrently. You must either explicitly control access to the connection
|
||||
(using mutexes) or use a connection for each thread. If each thread uses its own connection,
|
||||
you will need to use the AT clause to specify which connection the thread will use.
|
||||
(using mutexes) or use a connection for each thread.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
@ -249,7 +248,7 @@ EXEC SQL AT <replaceable>connection-name</replaceable> SELECT ...;
|
||||
EXEC SQL SET CONNECTION <replaceable>connection-name</replaceable>;
|
||||
</programlisting>
|
||||
This option is particularly convenient if many statements are to be
|
||||
executed on the same connection. It is not thread-aware.
|
||||
executed on the same connection.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
|
Loading…
Reference in New Issue
Block a user