Rewording, use the more common multi-threaded/single-threaded.
authorBruce Momjian <[email protected]>
Thu, 13 Oct 2005 17:55:18 +0000 (17:55 +0000)
committerBruce Momjian <[email protected]>
Thu, 13 Oct 2005 17:55:18 +0000 (17:55 +0000)
doc/src/sgml/ecpg.sgml
doc/src/sgml/libpq.sgml

index 4356d80e7e9986c459c1d2973b78843d4f51afe2..09dbd6bd76213eafb01446ec55123a36fdb8e276 100644 (file)
@@ -1613,8 +1613,9 @@ ECPG = ecpg
     compiled with different flags, this function call will crash the 
     application because the internal representation of the 
     <literal>FILE</> pointers differ.  Specifically,
-    threading/non-threading, release/debug, and static/dynamic flags should 
-    be the same for the library and all applications using that library.
+    multi-threaded/single-threaded, release/debug, and static/dynamic 
+    flags should be the same for the library and all applications using
+    that library.
     </para>
     </note>
    </listitem>
index 465847699604a32198e00abbcaad0d7090155624..6e0fe97f99cc269479559c7105c7a39b8151e5ff 100644 (file)
@@ -3520,9 +3520,9 @@ void PQtrace(PGconn *conn, FILE *stream);
 On Win32, if the <application>libpq</> library and an application are
 compiled with different flags, this function call will crash the 
 application because the internal representation of the <literal>FILE</> 
-pointers differ.  Specifically, threading/non-threading, release/debug, and
-static/dynamic flags should be the same for the library and all applications
-using that library.
+pointers differ.  Specifically, multi-threaded/single-threaded,
+release/debug, and static/dynamic flags should be the same for the
+library and all applications using that library.
 </para>
 </note>
 </listitem>