AW: Re: SOMAXCONN (was Re: Solaris source code)

From: Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at>
To: "'ncm(at)zembu(dot)com'" <ncm(at)zembu(dot)com>
Cc: "'pgsql-hackers(at)postgresql(dot)org'" <pgsql-hackers(at)postgresql(dot)org>
Subject: AW: Re: SOMAXCONN (was Re: Solaris source code)
Date: 2001-07-12 08:14:44
Message-ID: 11C1E6749A55D411A9670001FA68796336837F@sdexcsrv1.f000.d0188.sd.spardat.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


> The question is really whether you ever want a client to get a
> "rejected" result from an open attempt, or whether you'd rather they
> got a report from the back end telling them they can't log in. The
> second is more polite but a lot more expensive. That expense might
> really matter if you have MaxBackends already running.

One of us has probably misunderstood the listen parameter.
It only limits the number of clients that can connect concurrently.
It has nothing to do with the number of clients that are already connected.
It sort of resembles a maximum queue size for the accept loop.
Incoming connections fill the queue, accept frees the queue by taking the
connection to a newly forked backend.

Andreas

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Vadim Mikheev 2001-07-12 08:36:31 Re: Strangeness in xid allocation / snapshot setup
Previous Message markMLl.pgsql-general 2001-07-12 08:02:03 Re: 2 gig file size limit