Re: PostGres Doubt

From: David Ford <david+cert(at)blue-labs(dot)org>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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-14 13:19:03
Message-ID: 3D09ED47.3030905@blue-labs.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

pg_auth=# select version();
version
------------------------------------------------------------
PostgreSQL 7.2 on i686-pc-linux-gnu, compiled by GCC 3.0.2

Which btw has a curious grant/revoke bug. create foo; grant select on
foo to bar; results in all rights being granted. You must revoke and
grant again in order to get the correct rights set.

If this rights bug has been fixed, I'll upgrade, but I don't consider it
a big problem since I am well aware of the bug.

David

Bruce Momjian wrote:

>David Ford wrote:
>
>
>>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.
>>
>>
>
>Wow, I am confused. md5 should be fine. Certainly sounds like there is
>a thread problem with PQconnectdb(). Are you using 7.2.X?
>
>
>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2002-06-14 13:48:54 Re: Language Comments
Previous Message Dave Page 2002-06-14 10:10:52 Language Comments