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-13 08:36:13
Message-ID: 11C1E6749A55D411A9670001FA687963368385@sdexcsrv1.f000.d0188.sd.spardat.at
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


> When the system is too heavily loaded (however measured), any further
> login attempts will fail. What I suggested is, instead of the
> postmaster accept()ing the connection, why not leave the connection
> attempt in the queue until we can afford a back end to handle it?

Because the clients would time out ?

> Then, the argument to listen() will determine how many attempts can
> be in the queue before the network stack itself rejects them without
> the postmaster involved.

You cannot change the argument to listen() at runtime, or are you suggesting
to close and reopen the socket when maxbackends is reached ? I think
that would be nonsense.

I liked the idea of min(MaxBackends, PG_SOMAXCONN), since there is no use in
accepting more than your total allowed connections concurrently.

Andreas

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message mlw 2001-07-13 11:53:02 Re: AW: Re: SOMAXCONN (was Re: Solaris source code)
Previous Message Zeugswetter Andreas SB 2001-07-13 08:19:59 AW: Re: [GENERAL] Vacuum and Transactions