Document the SSL and Kerberos are not thread-safe.

diff --git a/doc/src/sgml/libpq.sgml b/doc/src/sgml/libpq.sgml
index ec1324c810c3bf75baf076cac0b5b10612f3f60a..82b8099a4a0b2fb72a3bae66b3d4be920361990a 100644 (file)
--- a/doc/src/sgml/libpq.sgml
+++ b/doc/src/sgml/libpq.sgml
@@ -1,5 +1,5 @@
 
 
  
@@ -3630,7 +3630,8 @@ call fe_setauthsvc at all.
 crypt() operating system function, which is often
 not thread-safe.cryptthread
 safety It is better to use the md5 method,
-which is thread-safe on all platforms.
+which is thread-safe on all platforms.  SSL connections
+and kerberos authentication are also not thread-safe.
 
 
 
@@ -3645,7 +3646,7 @@ completion. When --enable-thread-safety is used,
 before the first database connection if no custom SIGPIPE
 handler has been installed previously. This handler uses thread-local
 storage to determine if a SIGPIPE signal has been generated
-by an internal send(). If an application wants to install
+by a libpq send(). If an application wants to install
 its own SIGPIPE signal handler, it should call
 PQinSend() to determine if it should ignore the
 SIGPIPE signal. This function is available in both