Reini Urban said:
>> Tom Lane wrote:
>>>Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
>>>>What has changed in the last 3 weeks is that I refreshed my Cygwin
>>>> installation, I think when I was wrestling with the NLS thing. If
>>>> nothing in postgres has changed in this area I assume that platform
>>>> changes account for the regression.
>>>Sounds that way to me too, but it's disturbing. One would say they
>>> broke their scheduler :-(. Possibly you should try to stir up some
>>> interest among the Cygwin hackers in looking into this.
>> I'd like somebody else to report the same phenomenon first. Reini?
> Why plperl is broken I cannot say yet.
> I still have the same general IPC permission problem since about beta3.
> Only very few cygwin hackers have this also.
> I only got confirmation that the problem is in postgresql, not in
Hmm. Well, JimB got the same result yesterday that I have been seeing (the
stats regression test failure), so I consider that sufficient confoirmation.
I'm not quite sure what question I should be asking of the Cygwin people.
Tom, Can you suggest something?
I'll look at the plperl thing. That has also prompted me to add a buildfarm
feature request to test perl, python and tcl if they are configured in.
In response to
pgsql-hackers by date
|Next:||From: Tom Lane||Date: 2005-03-29 14:45:17|
|Subject: Re: minor windows & cygwin regression failures on stable |
|Previous:||From: Reini Urban||Date: 2005-03-29 12:29:43|
|Subject: Re: minor windows & cygwin regression failures on stable|