Re: PostGres Doubt
От | David Ford |
---|---|
Тема | Re: PostGres Doubt |
Дата | |
Msg-id | 3D092EC8.5040608@blue-labs.org обсуждение исходный текст |
Ответ на | Re: PostGres Doubt ("Dann Corbit" <DCorbit@connx.com>) |
Ответы |
Re: PostGres Doubt
Re: PostGres Doubt |
Список | pgsql-hackers |
I'm using md5 in pg_hba.conf. That is the method, no? I'm writing a milter application which instantiates a private resource for each thread upon thread startup. I have priv->conn which I establish as priv->conn=PQconnectdb(connstr), connstr is const char *connstr="host=10.0.0.5 dbname=bmilter user=username password=password"; It segfaults depending on it's mood but it tends to happen about 50-70% of the time. I switched to PQsetdbLogin() which has worked perfectly. I don't really want to use that however, I would muchprefer using my connstr. Am I missing something? Thanks, David Tom Lane wrote: >David Ford <david+cert@blue-labs.org> writes: > > >>So reentrancy in libpq basically is put on hold until 7.3. >> >> > >Only if you insist on using "crypt", which is deprecated anyway. >md5 is the preferred encryption method. > >My feeling about the proposed patch was that crypt is now a legacy auth >method, and it's not clear that we should create platform/library >dependencies just to support making multiple connections simultaneously >under crypt auth. (Note that *using* connections concurrently is not >at issue, only whether you can execute the authentication phase of >startup concurrently.) > > regards, tom lane > >
В списке pgsql-hackers по дате отправления: