|
1 |
| -<!-- $PostgreSQL: pgsql/doc/src/sgml/ecpg.sgml,v 1.91 2009/09/18 13:13:32 meskes Exp $ --> |
| 1 | +<!-- $PostgreSQL: pgsql/doc/src/sgml/ecpg.sgml,v 1.92 2009/11/30 14:47:37 momjian Exp $ --> |
2 | 2 |
|
3 | 3 | <chapter id="ecpg">
|
4 | 4 | <title><application>ECPG</application> - Embedded <acronym>SQL</acronym> in C</title>
|
@@ -352,13 +352,13 @@ EXEC SQL AT <replaceable>connection-name</replaceable> SELECT ...;
|
352 | 352 | </programlisting>
|
353 | 353 | This option is particularly suitable if the application needs to
|
354 | 354 | use several connections in mixed order.
|
355 |
| -</para> |
| 355 | + </para> |
356 | 356 |
|
357 |
| -<para> |
358 |
| -If your application uses multiple threads of execution, they cannot share a |
359 |
| -connection concurrently. You must either explicitly control access to the connection |
360 |
| -(using mutexes) or use a connection for each thread. If each thread uses its own connection, |
361 |
| -you will need to use the AT clause to specify which connection the thread will use. |
| 357 | + <para> |
| 358 | + If your application uses multiple threads of execution, they cannot share a |
| 359 | + connection concurrently. You must either explicitly control access to the connection |
| 360 | + (using mutexes) or use a connection for each thread. If each thread uses its own connection, |
| 361 | + you will need to use the AT clause to specify which connection the thread will use. |
362 | 362 | </para>
|
363 | 363 |
|
364 | 364 | <para>
|
|