Re: Doing authentication in backend

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Doing authentication in backend
Date: 2001-06-16 17:02:15
Message-ID: 28221.992710935@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

ncm(at)zembu(dot)com (Nathan Myers) writes:
> On Thu, Jun 14, 2001 at 01:42:26PM -0400, Tom Lane wrote:
>> Also note that we could easily fix things so that the max-number-of-
>> backends limit is not checked until we have passed the authentication
>> procedure. A PM child that's still busy authenticating doesn't have
>> to count.

> And impose a very short timeout on authentication.

Yes. There's no time limit at present, but it will be easy to add one
after we change to fork-before-authenticate (since each PM child can
have its own itimer).

> This last could also be addressed (along with Solaris's Unix Sockets
> problem!) by changing the second argument to listen(2) from the current
> SOMAXCONN -- which is 5 in Solaris 2.7 -- to 127. See the six-page
> discussion in Stevens UNPv1 beginning at page 93.

Unfortunately I only have Stevens' first edition, and it doesn't seem
to have any such advice in it. Why is it a good idea to ignore the
platform's specification of SOMAXCONN? Seems like on non-broken
platforms, that would do more harm than good.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2001-06-16 17:05:53 Re: RTLD_GLOBAL on openbsd
Previous Message Tom Lane 2001-06-16 16:54:53 Re: [HACKERS] Postgres