diff options
| author | Michael Meskes <meskes@postgresql.org> | 2017-06-06 12:19:28 +0200 |
|---|---|---|
| committer | Michael Meskes <meskes@postgresql.org> | 2017-06-06 12:20:31 +0200 |
| commit | 0f33ee0e3b7527fb0c88abf0ae8a49a9c38d9c0e (patch) | |
| tree | 8db328593404a81f9978b4b8876056683419664b | |
| parent | c1abe6c786d8f00643de8519140d77644b474163 (diff) | |
| download | postgresql-0f33ee0e3b7527fb0c88abf0ae8a49a9c38d9c0e.tar.gz postgresql-0f33ee0e3b7527fb0c88abf0ae8a49a9c38d9c0e.zip | |
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 dead4c3f869..f13a0e999f2 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> |