AW: Re: SOMAXCONN (was Re: Solaris source code) - Mailing list pgsql-hackers

From Zeugswetter Andreas SB
Subject AW: Re: SOMAXCONN (was Re: Solaris source code)
Date
Msg-id 11C1E6749A55D411A9670001FA68796336837F@sdexcsrv1.f000.d0188.sd.spardat.at
Whole thread Raw
Responses Re: Re: SOMAXCONN (was Re: Solaris source code)  (ncm@zembu.com (Nathan Myers))
List 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


pgsql-hackers by date:

Previous
From: "Vadim Mikheev"
Date:
Subject: Re: Strangeness in xid allocation / snapshot setup
Next
From: "V. M."
Date:
Subject: Child itemid in update-chain marked as unused - can't continue repair_frag