| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, Ian Lance Taylor <ian(at)zembu(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Re: SOMAXCONN (was Re: Solaris source code) |
| Date: | 2001-07-11 17:13:45 |
| Message-ID: | 200107111713.f6BHDkr15617@candle.pha.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> > Tom Lane writes:
> >> 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...
>
> > Would anything computed from the maximum number of allowed connections
> > make sense?
>
> [ looks at code ... ] Hmm, MaxBackends is indeed set before we arrive
> at the listen(), so it'd be possible to use MaxBackends to compute the
> parameter. Offhand I would think that MaxBackends or at most
> 2*MaxBackends would be a reasonable value.
Don't we have maxbackends configurable at runtime. If so, any constant
we put in config.h will be inaccurate. Seems we have to track
maxbackends.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2001-07-11 17:18:33 | Re: Re: SOMAXCONN (was Re: Solaris source code) |
| Previous Message | Bruce Momjian | 2001-07-11 17:02:49 | Re: Re: Encrypting pg_shadow passwords |