From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Andrew Dunstan" <andrew(at)dunslane(dot)net> |
Cc: | pgsql-hackers-win32(at)postgresql(dot)org |
Subject: | Re: regression failures - further data |
Date: | 2004-05-07 02:32:50 |
Message-ID: | 27576.1083897170@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers-win32 |
"Andrew Dunstan" <andrew(at)dunslane(dot)net> writes:
> Tom Lane said:
>> "Andrew Dunstan" <andrew(at)dunslane(dot)net> writes:
>>> No, this is running with the patch that suppresses that. Basically,
>>> for some reason that I have been unable to find, and which leaves no
>>> log trace, copy just stops after about 4 or 5 lines, and then there
>>> are a bunch of consequent failures.
>> That seems *really weird*. When you say "stops after 4 or 5 lines", do
>> you mean that the first few rows of the source data get committed
>> successfully, but the rest don't?
> Er, no :-) I mean the first few lines of source code ... around where it
> does the "delete from onek".
Oh, you mean the copy regression script stops.
Is it possible that it didn't fail, per se, but simply stopped making
progress?
Theoretically the regression script couldn't move on to later steps
until that script gets done, but it wouldn't be quite so weird to think
that that interlock failed ...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2004-05-07 07:27:14 | Re: regression failures - further data |
Previous Message | Andrew Dunstan | 2004-05-07 01:54:37 | Re: regression failures - further data |