11<!--
2- $Header: /cvsroot/pgsql/doc/src/sgml/libpq.sgml,v 1.86 2002/01/18 20:32:54 momjian Exp $
2+ $Header: /cvsroot/pgsql/doc/src/sgml/libpq.sgml,v 1.87 2002/01/18 20:39:04 momjian Exp $
33-->
44
55 <chapter id="libpq">
@@ -2114,13 +2114,6 @@ time. In particular, you cannot issue concurrent queries from different
21142114threads through the same connection object. (If you need to run
21152115concurrent queries, start up multiple connections.)
21162116</para>
2117- <para>
2118- However, <filename>libpq</filename> clients using the
2119- <literal>crypt</literal> encryption method rely on the
2120- <literal>crypt()</literal> operating system function, which often is not
2121- thread-safe. It is better to use <literal>MD5</literal> encryption,
2122- which is guarantted to be thread-safe on all platforms.
2123- </para>
21242117
21252118<para>
21262119<structname>PGresult</> objects are read-only after creation, and so can be passed around
@@ -2135,6 +2128,13 @@ replaced by <function>PQoidValue</function>. There is no good reason to
21352128call <function>fe_setauthsvc</function> at all.
21362129</para>
21372130
2131+ <para>
2132+ <filename>Libpq</filename> clients using the <literal>crypt</literal>
2133+ encryption method rely on the <literal>crypt()</literal> operating
2134+ system function, which is often not thread-safe. It is better to use
2135+ <literal>MD5</literal> encryption, which is thread-safe on all
2136+ platforms.
2137+ </para>
21382138</sect1>
21392139
21402140