database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-06-29 10:41:53 +03:00
Code Activity

I have applied the following patch to document PQinitSSL() and

Browse Source 
PQregisterThreadLock().

I also remove the crypt() mention in the libpq threading section and
added a single sentence in the client-auth manual page under crypt().
Crypt authentication is so old now that a separate paragraph about it
seemed unwise.

I also added a comment about our use of locking around pqGetpwuid().
This commit is contained in:
Bruce Momjian
2005-10-24 15:38:37 +00:00
parent 18feafcc59
commit 819159709f
4 changed files with 32 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
src/interfaces/libpq/fe-auth.c
View File

@ -10,7 +10,7 @@
* exceed INITIAL_EXPBUFFER_SIZE (currently 256 bytes).
*
* IDENTIFICATION
* $PostgreSQL: pgsql/src/interfaces/libpq/fe-auth.c,v 1.106 2005/10/17 16:24:20 tgl Exp $
* $PostgreSQL: pgsql/src/interfaces/libpq/fe-auth.c,v 1.107 2005/10/24 15:38:37 momjian Exp $
*
*-------------------------------------------------------------------------
*/
@ -500,6 +500,16 @@ pg_fe_getauthname(char *PQerrormsg)
struct passwd *pw = NULL;
#endif
/*
* pglock_thread() really only needs to be called around
* pg_krb5_authname(), but some users are using configure
* --enable-thread-safety-force, so we might as well do
* the locking within our library to protect pqGetpwuid().
* In fact, application developers can use getpwuid()
* in their application if they use the locking call we
* provide, or install their own locking function using
* PQregisterThreadLock().
*/
pglock_thread();
#ifdef KRB5