diff options
| author | Michael Meskes <meskes@postgresql.org> | 2017-06-06 12:19:28 +0200 |
|---|---|---|
| committer | Michael Meskes <meskes@postgresql.org> | 2017-06-07 16:14:34 +0200 |
| commit | 32afb2b5628455a8de2f5169211651cfe7e4815f (patch) | |
| tree | 15a8e0b659dda10b55cf7e72fb6a96b405bb02e5 | |
| parent | f44c609ea014fc642431bb5b0adbb120033f8cb1 (diff) | |
Fix docs to not claim ECPG's SET CONNECTION is not thread-aware.
Changed by: Tsunakawa, Takayuki <tsunakawa.takay@jp.fujitsu.com>
| -rw-r--r-- | doc/src/sgml/ecpg.sgml | 5 |
1 files changed, 2 insertions, 3 deletions
diff --git a/doc/src/sgml/ecpg.sgml b/doc/src/sgml/ecpg.sgml index cb9ab34dbfd..8cdc852a04a 100644 --- a/doc/src/sgml/ecpg.sgml +++ b/doc/src/sgml/ecpg.sgml @@ -240,8 +240,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> @@ -251,7 +250,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> |