| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | pgsql-hackers-win32 <pgsql-hackers-win32(at)postgresql(dot)org> |
| Subject: | Re: regression failures - further data |
| Date: | 2004-05-06 22:09:52 |
| Message-ID: | 200405062209.i46M9qt11674@candle.pha.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers-win32 |
Andrew Dunstan wrote:
>
> I have managed (with a lot of effort) to track down the apparent cause
> of the regression failures I was seeing. They appear to be directly
> related to the degree of parallelism with which the tests are run. I can
> reliably get a 100% clean run on the serial tests, and on the parallel
> tests with MAX_CONNECTIONS=5. But if I run at MAX_CONNECTIONS=10 I
> (almost) always get failures, which for some reason that is beyond me
> start with the copy test, which isn't even run in parallel with other tests.
>
> This is all quite worrying, and suggests that we will need to do some
> careful stress testing before we can release this.
>
> Is there some W2K parameter I can tweak in the TCP stack that might
> alleviate the problem?
Is this the extra newline regression failure you were seeing?
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2004-05-06 22:51:41 | Re: regression failures - further data |
| Previous Message | Andrew Dunstan | 2004-05-06 21:09:27 | regression failures - further data |