From: | David Ford <david+cert(at)blue-labs(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Dann Corbit <DCorbit(at)connx(dot)com>, vikas p verma <vvicky72(at)rediffmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: PostGres Doubt |
Date: | 2002-06-13 23:46:16 |
Message-ID: | 3D092EC8.5040608@blue-labs.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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 much prefer using my
connstr.
Am I missing something?
Thanks,
David
Tom Lane wrote:
>David Ford <david+cert(at)blue-labs(dot)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
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2002-06-13 23:55:52 | Re: Making serial survive pg_dump |
Previous Message | Rod Taylor | 2002-06-13 22:11:05 | Re: Making serial survive pg_dump |