aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>2003-12-01 22:36:40 +0000
committerBruce Momjian <bruce@momjian.us>2003-12-01 22:36:40 +0000
commit8f61184db70be4650db72b14f9fe3487b4230ff7 (patch)
treea29a0c703ddfc04a3c2eebeaad130bdc4acd1baf
parent8c4af96fb026333b8dc592e0c06715cf5aefa7e0 (diff)
downloadpostgresql-8f61184db70be4650db72b14f9fe3487b4230ff7.tar.gz
postgresql-8f61184db70be4650db72b14f9fe3487b4230ff7.zip
Hi, this doco patch is a quick one to add explicit mention of the need
for the AT clause in threaded ECPG applications. Philip Yarra
-rw-r--r--doc/src/sgml/ecpg.sgml9
1 files changed, 8 insertions, 1 deletions
diff --git a/doc/src/sgml/ecpg.sgml b/doc/src/sgml/ecpg.sgml
index 2c113385de1..27aca4e60ea 100644
--- a/doc/src/sgml/ecpg.sgml
+++ b/doc/src/sgml/ecpg.sgml
@@ -1,5 +1,5 @@
<!--
-$PostgreSQL: pgsql/doc/src/sgml/ecpg.sgml,v 1.56 2003/11/29 19:51:36 pgsql Exp $
+$PostgreSQL: pgsql/doc/src/sgml/ecpg.sgml,v 1.57 2003/12/01 22:36:40 momjian Exp $
-->
<chapter id="ecpg">
@@ -353,6 +353,13 @@ EXEC SQL AT <replaceable>connection-name</replaceable> SELECT ...;
</programlisting>
This option is particularly suitable if the application needs to
use several connections in mixed order.
+ </para>
+
+ <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.
</para>
<para>