|
1 | 1 | <!-- |
2 | | -$PostgreSQL: pgsql/doc/src/sgml/ecpg.sgml,v 1.56 2003/11/29 19:51:36 pgsql Exp $ |
| 2 | +$PostgreSQL: pgsql/doc/src/sgml/ecpg.sgml,v 1.57 2003/12/01 22:36:40 momjian Exp $ |
3 | 3 | --> |
4 | 4 |
|
5 | 5 | <chapter id="ecpg"> |
@@ -353,6 +353,13 @@ EXEC SQL AT <replaceable>connection-name</replaceable> SELECT ...; |
353 | 353 | </programlisting> |
354 | 354 | This option is particularly suitable if the application needs to |
355 | 355 | use several connections in mixed order. |
| 356 | + </para> |
| 357 | + |
| 358 | + <para> |
| 359 | + If your application uses multiple threads of execution, they cannot share a |
| 360 | + connection concurrently. You must either explicitly control access to the connection |
| 361 | + (using mutexes) or use a connection for each thread. If each thread uses its own connection, |
| 362 | + you will need to use the AT clause to specify which connection the thread will use. |
356 | 363 | </para> |
357 | 364 |
|
358 | 365 | <para> |
|