| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: max client limit in pgbench |
| Date: | 2007-08-25 03:05:02 |
| Message-ID: | 26458.1188011102@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tatsuo Ishii <ishii(at)postgresql(dot)org> writes:
> This is used for calculating the upper limit of -c option. However
> actual limit is coming from the number of descriptors that select(2)
> can watch (besides the number of file descriptors allowed by the
> kernal. This is different story though, I think). So it seems the line
> would be better looking at FD_SETSIZE in select.h.
This seems reasonable, but surely it needs to be FD_SETSIZE less a bit,
because stdin/stdout/etc eat FD numbers too. Maybe
#define MAXCLIENTS (FD_SETSIZE - 10)
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2007-08-25 03:44:27 | buildfarm interruption |
| Previous Message | Tatsuo Ishii | 2007-08-25 02:50:11 | max client limit in pgbench |