Re: PostGres Doubt

From: Hannu Krosing <hannu(at)tm(dot)ee>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: David Ford <david+cert(at)blue-labs(dot)org>, 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 10:20:18
Message-ID: 1023963618.12488.0.camel@taru.tm.ee
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, 2002-06-12 at 19:38, 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.)

can't this be solved by simple locking ?

I know that postgres team can do locking properly ;)

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Hannu Krosing 2002-06-13 10:26:11 Re: Feature request: Truncate table
Previous Message Michael Meskes 2002-06-13 10:09:12 Re: PostGres Doubt