Andrew,
> > > Something like this?
> > > make MAX_CONNECTIONS=10 check
AFAICT, non-server Windows versions have a listen backlog of 5:
http://support.microsoft.com/support/kb/articles/Q127/1/44.asp
http://216.239.57.104/search?q=cache:Ll4KYYj_BB8J:www.microsoft.com/windows2000/docs/
The number isn't hardcoded at all (except for the warning on gygwin if you
choose some high value) - you can choose whatever value you like at run time
(even 1). This will be documented.
10 works for me on my XP-HE/cygwin installation, though. YMMV I guess.
cheers
andrew
- Original Message
I notice that the current GiST docs are pretty crazy. Here's my first
attempt at actually making them useful.
(http://developer.postgresql.org/docs/postgres/gist.html)
Interestingly enough, I had a chat with Joe Hellerstein while trying to
write this - he was interested in how GiST was going i
Andrew,
On Wed, Oct 29, 2003 at 08:45:30AM -0500, Andrew Dunstan wrote:
> The number isn't hardcoded at all
Understood.
> (except for the warning on gygwin if you choose some high value)
The above is my concern -- sorry, for being unclear.
> - you can choose whatever value you like at run time
Jason Tishler wrote:
Andrew,
On Wed, Oct 29, 2003 at 08:45:30AM -0500, Andrew Dunstan wrote:
The number isn't hardcoded at all
Understood.
(except for the warning on gygwin if you choose some high value)
The above is my concern -- sorry, for being unclear.
I don't want to issue
Andrew,
On Wed, Oct 29, 2003 at 11:34:34AM -0500, Andrew Dunstan wrote:
> I don't want to issue a warning on a setting that is likely to succeed
> in some cases. How about this instead of what I had - it deals with
> the most likely problem case?:
>
> # --
> # warn of cygwin likely failur
