postgres.git / summary / log / commit / refs

commit    ccd717a2e8a5b59f5117ce3dc6e28f71bda9a030
Author:   Michael Meskes <meskes@postgresql.org>
Date:     Tue Jun 06 10:19:28 2017 +0000

    Fix docs to not claim ECPG's SET CONNECTION is not thread-aware.
    
    Changed by: Tsunakawa, Takayuki <tsunakawa.takay@jp.fujitsu.com>


 doc/src/sgml/ecpg.sgml | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/doc/src/sgml/ecpg.sgml b/doc/src/sgml/ecpg.sgml
index 849a95ff22f..89aa2305869 100644
--- a/doc/src/sgml/ecpg.sgml
+++ b/doc/src/sgml/ecpg.sgml
@@ -238,8 +238,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>
@@ -249,7 +248,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>


[parent: 133b1920c5b8]