Re: PostgreSQL 6.2.5 Visual Studio Build does not pass the regression tests.

From: "Shiv Shivaraju Gowda (shivshi)" <shivshi(at)cisco(dot)com>
To: Noah Misch <noah(at)leadboat(dot)com>
Cc: "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: PostgreSQL 6.2.5 Visual Studio Build does not pass the regression tests.
Date: 2014-03-05 22:00:12
Message-ID: CF3CD6F2.13A26%shivshi@cisco.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs


> Do you use any anti-malware software on all of those systems?

Yes they come pre-installed, but in one of the system I tested I tried my
best to disable all the ones I knew.

> No; that approximately describes the Cygwin build.

OK, in that case I don¹t why we don¹t hit the problem with MinGW. May be
it is the same reason why other people are not seeing this on VS build,
i.e
WAIT_IO_COMPLETION is not triggered somehow.

We are testing w32-io-completion-v1.patch, will keep you posted.

On 3/4/14, 8:22 AM, "Noah Misch" <noah(at)leadboat(dot)com> wrote:

>[Please use reply-to-all to keep me on the recipients list.]
>
>On Thu, Feb 27, 2014 at 01:43:20PM -0800, shivshi wrote:
>> > Please tell us as much as possible about the OS configurations that
>>have
>> > exhibited the problem and the OS configurations that have *not*
>>exhibited
>> > the problem with the same binaries.
>>
>> The OS configuration that has exhibited the problem is Windows 7
>>Enterprise,
>> 64 bit OS on Intel Core-I7.
>> We are not aware of a OS configuration on which this did work.
>
>Do you use any anti-malware software on all of those systems?
>
>> > A MinGW build certainly includes win32_sema.c, and I don't see why it
>> > wouldn't use that code path. How did you determine that?
>>
>> I thought the MinGW build which is built with gnu compiler invokes Posix
>> libraries and doesn't call into Windows System calls directly.
>
>No; that approximately describes the Cygwin build.
>
>> > Would you verify that the attached patch fixes your builds?
>>
>> Do you want me to go ahead with the tests or do you want me to wait to
>> incorporate Tom Lane's suggestions
>
>Please go ahead and test w32-io-completion-v1.patch.
>
>--
>Noah Misch
>EnterpriseDB http://www.enterprisedb.com

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2014-03-05 23:46:44 Re: BUG #9398: DELETE refering to a materialized view produces "cannot lock rows in materialized view" error
Previous Message Alex Hunsaker 2014-03-05 19:55:14 Re: [BUGS] BUG #9223: plperlu result memory leak