From a724463c8ae3fc3f1d2bd3dfde374eb0f15d0538 Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Fri, 18 Jan 2002 20:39:04 +0000 Subject: [PATCH] Improve non-thread-safe mention of libpq's crypt. --- doc/src/sgml/libpq.sgml | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/doc/src/sgml/libpq.sgml b/doc/src/sgml/libpq.sgml index 3e9fb16ef3c..d487cce5cc3 100644 --- a/doc/src/sgml/libpq.sgml +++ b/doc/src/sgml/libpq.sgml @@ -1,5 +1,5 @@ @@ -2114,13 +2114,6 @@ time. In particular, you cannot issue concurrent queries from different threads through the same connection object. (If you need to run concurrent queries, start up multiple connections.) - -However, libpq clients using the -crypt encryption method rely on the -crypt() operating system function, which often is not -thread-safe. It is better to use MD5 encryption, -which is guarantted to be thread-safe on all platforms. - PGresult objects are read-only after creation, and so can be passed around @@ -2135,6 +2128,13 @@ replaced by PQoidValue. There is no good reason to call fe_setauthsvc at all. + +Libpq clients using the crypt +encryption method rely on the crypt() operating +system function, which is often not thread-safe. It is better to use +MD5 encryption, which is thread-safe on all +platforms. +