11<!--
2- $PostgreSQL: pgsql/doc/src/sgml/libpq.sgml,v 1.146 2004/01/26 22:13:21 neilc Exp $
2+ $PostgreSQL: pgsql/doc/src/sgml/libpq.sgml,v 1.147 2004/03/11 02:39:10 momjian Exp $
33-->
44
55 <chapter id="libpq">
@@ -3630,7 +3630,8 @@ call <function>fe_setauthsvc</function> at all.
36303630<literal>crypt()</literal> operating system function, which is often
36313631not thread-safe.<indexterm><primary>crypt</><secondary>thread
36323632safety</></> It is better to use the <literal>md5</literal> method,
3633- which is thread-safe on all platforms.
3633+ which is thread-safe on all platforms. <application>SSL</> connections
3634+ and <application>kerberos</> authentication are also not thread-safe.
36343635</para>
36353636
36363637<para>
@@ -3645,7 +3646,7 @@ completion. When <literal>--enable-thread-safety</> is used,
36453646before the first database connection if no custom <literal>SIGPIPE</>
36463647handler has been installed previously. This handler uses thread-local
36473648storage to determine if a <literal>SIGPIPE</> signal has been generated
3648- byan internal <function>send()</>. If an application wants to install
3649+ bya libpq <function>send()</>. If an application wants to install
36493650its own <literal>SIGPIPE</> signal handler, it should call
36503651<function>PQinSend()</> to determine if it should ignore the
36513652<literal>SIGPIPE</> signal. This function is available in both