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
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
On Tue, Jul 10, 2001 at 05:06:28PM -0400, Bruce Momjian wrote:
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
Bruce Momjian [EMAIL PROTECTED] writes:
Could we test SOMAXCONN and set PG_SOMAXCONN to 1000 only if SOMAXCONN1
is less than 1000?
Why bother?
If you've got some plausible scenario where 1000 is too small, we could
just as easily make it 1. I don't see the need for yet another
configure
Bruce Momjian [EMAIL PROTECTED] writes:
I was thinking:
#if SOMAXCONN = 1000
#define PG_SOMAXCONN SOMAXCONN
#else
#define PG_SOMAXCONN 1000
#endif
Not in config.h, you don't. Unless you want sys/socket.h (or
whichever header defines SOMAXCONN; how consistent
On Tue, Jul 10, 2001 at 06:36:21PM -0400, Tom Lane wrote:
[EMAIL PROTECTED] (Nathan Myers) writes:
All the OSes we know of fold it to 128, currently. We can jump it
to 10240 now, or later when there are 20GHz CPUs.
If you want to make it more complicated, it would be more useful to
[EMAIL PROTECTED] (Nathan Myers) writes:
All the OSes we know of fold it to 128, currently. We can jump it
to 10240 now, or later when there are 20GHz CPUs.
If you want to make it more complicated, it would be more useful to
be able to set the value lower for runtime environments
[EMAIL PROTECTED] (Nathan Myers) writes:
All the OSes we know of fold it to 128, currently. We can jump it
to 10240 now, or later when there are 20GHz CPUs.
If you want to make it more complicated, it would be more useful to
be able to set the value lower for runtime environments where PG
