hcq/MaxScale
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Use SQLITE_OPEN_NOMUTEX for session specific sqlite3 handles in PAM auth

Browse Source
This commit is contained in:
Esa Korhonen
2018-01-03 14:35:19 +02:00
parent a6914ebefe
commit c45a8abc20
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
server/modules/authenticator/PAM/PAMAuth/pam_client_session.cc
View File

@ -203,9 +203,9 @@ PamClientSession:: ~PamClientSession()
PamClientSession* PamClientSession::create(const PamInstance& inst) PamClientSession* PamClientSession::create(const PamInstance& inst)
{ {
int db_flags = SQLITE_OPEN_READONLY | SQLITE_OPEN_SHAREDCACHE; // This handle is only used from one thread, can define no_mutex.
sqlite3* dbhandle = NULL; sqlite3* dbhandle = NULL;
// This handle is only used from one thread int db_flags = SQLITE_OPEN_READONLY | SQLITE_OPEN_SHAREDCACHE | SQLITE_OPEN_NOMUTEX;
if (sqlite3_open_v2(inst.m_dbname.c_str(), &dbhandle, db_flags, NULL) == SQLITE_OK) if (sqlite3_open_v2(inst.m_dbname.c_str(), &dbhandle, db_flags, NULL) == SQLITE_OK)
{ {
sqlite3_busy_timeout(dbhandle, 1000); sqlite3_busy_timeout(dbhandle, 1000);