Re: "make check" improvement for cygwin

Tom Lane wrote:

>"Andrew Dunstan" <andrew@dunslane.net> writes:
>
>
>>Well, I posted the note last night but I finished the patch today, because
>>it was very simple and took so little time.
>>
>>
>
>I've committed this with the later revision about the warning message,
>and some other minor cleanups.  I added documentation in the "Regression
>Tests" chapter, but if there is anyplace else you want to mention it,
>send in a docs patch.
>
>
>

Thanks, Tom! I just sat down to do this work and saw your note.

This looks fine - the only other place it needs to be mentioned is in
FAQ_MSWIN I think.

patch for that attached.

cheers

andrew
Index: FAQ_MSWIN
===================================================================
RCS file: /projects/cvsroot/pgsql-server/doc/FAQ_MSWIN,v
retrieving revision 1.15
diff -c -w -r1.15 FAQ_MSWIN
*** FAQ_MSWIN    11 Nov 2002 20:04:05 -0000    1.15
--- FAQ_MSWIN    3 Nov 2003 03:50:09 -0000
***************
*** 51,56 ****

  2.  make check can generate spurious regression test failures due to
      overflowing the listen() backlog queue which causes connection
!     refused errors.

  Problem reports can be sent to pgsql-cygwin@postgresql.org.
--- 51,59 ----

  2.  make check can generate spurious regression test failures due to
      overflowing the listen() backlog queue which causes connection
!     refused errors or hangs. You can limit the number of connections
!     using the MAX_CONNECTIONS option thus:
!       make MAX_CONNECTIONS=5 check
!     (on some systems you can have up to about 10 simultaneous connections).

  Problem reports can be sent to pgsql-cygwin@postgresql.org.