> Mathijs Brands <[EMAIL PROTECTED]> writes: > > OK, I tried using 1024 (and later 128) instead of SOMAXCONN (defined to > > be 5 on Solaris) in src/backend/libpq/pqcomm.c and ran a few regression > > tests on two different Sparc boxes (Solaris 7 and 8). The regression > > test still fails, but for a different reason. The abstime test fails; > > not only on Solaris but also on FreeBSD (4.3-RELEASE). > > The abstime diff is to be expected (if you look closely, the test is > comparing 'current' to 'June 30, 2001'. Ooops). If that's the only > diff then you are in good shape. > > > Based on this and previous discussions, I am strongly tempted to remove > the use of SOMAXCONN and instead use, say, > > #define PG_SOMAXCONN 1000 > > defined in config.h.in. That would leave room for configure to twiddle > it, if that proves necessary. Does anyone know of a platform where this > would cause problems? AFAICT, all versions of listen(2) are claimed to > be willing to reduce the passed parameter to whatever they can handle. Could we test SOMAXCONN and set PG_SOMAXCONN to 1000 only if SOMAXCONN1 is less than 1000? -- Bruce Momjian | http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026 ---------------------------(end of broadcast)--------------------------- TIP 6: Have you searched our list archives? http://www.postgresql.org/search.mpl
