Re: PostGres Doubt - Mailing list pgsql-hackers

From Hannu Krosing
Subject Re: PostGres Doubt
Date
Msg-id 1023963618.12488.0.camel@taru.tm.ee
Whole thread Raw
In response to Re: PostGres Doubt  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Wed, 2002-06-12 at 19:38, 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.)

can't this be solved by simple locking ?

I know that postgres team can do locking properly ;)

--------------
Hannu



pgsql-hackers by date:

Previous
From: Tatsuo Ishii
Date:
Subject: Re: [PATCHES] Chinese GB18030 support is implemented!
Next
From: Hannu Krosing
Date:
Subject: Re: Feature request: Truncate table