Ian Lance Taylor <[EMAIL PROTECTED]> writes:
> But I wouldn't worry about it, and I wouldn't worry about Nathan's
> suggestion for making the limit configurable, because Postgres
> connections don't spend time on the queue. The postgres server will
> be picking them off as fast as it can. If the server can't pick
> processes off fast enough, then your system has other problems;
Right. Okay, it seems like just making it a hand-configurable entry
in config.h.in is good enough for now. When and if we find that
that's inadequate in a real-world situation, we can improve on it...
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
- [HACKERS] Re: SOMAXCONN (was Re: Solaris source code) Ian Lance Taylor
- Re: [HACKERS] Re: SOMAXCONN (was Re: Solaris source ... Tom Lane
- Re: [HACKERS] Re: SOMAXCONN (was Re: Solaris source ... Peter Eisentraut
- Re: [HACKERS] Re: SOMAXCONN (was Re: Solaris source ... Tom Lane
- Re: [HACKERS] Re: SOMAXCONN (was Re: Solaris sou... Nathan Myers
- Re: [HACKERS] Re: SOMAXCONN (was Re: Solaris source ... Bruce Momjian
- Re: [HACKERS] Re: SOMAXCONN (was Re: Solaris source ... Tom Lane
- Re: [HACKERS] Re: SOMAXCONN (was Re: Solaris sou... Bruce Momjian
- Re: [HACKERS] Re: SOMAXCONN (was Re: Solaris sou... Peter Eisentraut
- Re: [HACKERS] Re: SOMAXCONN (was Re: Solaris source ... Nathan Myers
- [HACKERS] Re: SOMAXCONN (was Re: Solaris source code... Nathan Myers
- Re: [HACKERS] Re: SOMAXCONN (was Re: Solaris source ... Peter Eisentraut
