Skip site navigation (1) Skip section navigation (2)

Re: Possibly corrupted shared memory, PostgreSQL 8.1 beta2, Windows 2000

From: "Jean-Pierre Pelletier" <pelletier_32(at)sympatico(dot)ca>
To: <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: Possibly corrupted shared memory, PostgreSQL 8.1 beta2, Windows 2000
Date: 2005-10-11 12:36:16
Message-ID: BAYC1-PASMTP02F16CFF2DEF64C02F80DB95780@CEZ.ICE (view raw or flat)
Thread:
Lists: pgsql-bugs
The antivirus is CA eTrust EZ v 7.0.6.7.

I cannot put back the antivirus on that server
because it is now in production mode.

Jean-Pierre Pelletier

----- Original Message ----- 
From: "Qingqing Zhou" <zhouqq(at)cs(dot)toronto(dot)edu>
To: <pgsql-bugs(at)postgresql(dot)org>
Sent: Friday, October 07, 2005 3:08 PM
Subject: Re: [BUGS] Possibly corrupted shared memory, PostgreSQL 8.1 beta2, 
Windows 2000


>
> ""Jean-Pierre Pelletier"" <pelletier_32(at)sympatico(dot)ca> wrote
>> Turning off the antivirus fixed the problem.
>> We haven't have any read/write/open error in more
>> than  two days.
>>
>> Thank you very much for your help and keep up the good work.
>>
>
> You are welcome :-) But I still suspect if this really solves the problem 
> ... by the way, may I know what anti-virus software are you using? And, if 
> it is possible, can you please turn on the anti-virus software again and 
> check the GetLastError()?
>
> A more detailed "guess" of the problem is here:
> http://archives.postgresql.org/pgsql-hackers/2005-07/msg00489.php
>
> Thanks a lot,
> Qingqing
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: if posting/reading through Usenet, please send an appropriate
>       subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
>       message can get through to the mailing list cleanly 


In response to

pgsql-bugs by date

Next:From: incheol yangDate: 2005-10-11 13:30:49
Subject: BUG #1955: trigger action on delete
Previous:From: Antonio MolinaDate: 2005-10-11 12:27:15
Subject: BUG #1954: Bug in to_date('09-10-2005', 'dd-mm-yyyy')

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group