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

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.

Our only remaining PostgreSQL problem is with pg_stat_actitivity
being unreliable and the statistics collector being restarted many times
every day.

Any idea what might be causing that?

Jean-Pierre Pelletier

----- Original Message -----
From: "Jean-Pierre Pelletier" <pelletier_32(at)sympatico(dot)ca>
To: "Qingqing Zhou" <zhouqq(at)cs(dot)toronto(dot)edu>
Cc: <pgsql-bugs(at)postgresql(dot)org>
Sent: Wednesday, October 05, 2005 2:58 PM
Subject: Re: [BUGS] Possibly corrupted shared memory, PostgreSQL 8.1 beta2,
Windows 2000

> I'll recompile with the trace that's no problem,
> and install the patched release tonight.
>
> After your last email, I've excluded the postgreSQL
> directory from the antivirus because I could do it without
> rebooting.
>
> I was also sometimes getting read/write or open
> error Invalid argument without the server crashing.
> After two days, if I haven't seen any of these
> error messages there is a very high chance that it's
> been fixed by turning off the antivirus.
>
> Jean-Pierre Pelletier
>
> ----- Original Message -----
> From: "Qingqing Zhou" <zhouqq(at)cs(dot)toronto(dot)edu>
> To: <pgsql-bugs(at)postgresql(dot)org>
> Sent: Wednesday, October 05, 2005 5:16 PM
> Subject: Re: [BUGS] Possibly corrupted shared memory, PostgreSQL 8.1
> beta2,
> Windows 2000
>
>
>>
>> ""Jean-Pierre Pelletier"" <pelletier_32(at)sympatico(dot)ca> wrote in message
>> news:003801c5c9b0$03e08500$6401a8c0(at)JP(dot)(dot)(dot)
>>>
>>> Yes, there is an antivirus software on the machine, a reboot is needed
>>> when it's turned off,
>>> I'll be allowed to reboot it tonight or I'll do it sooner if it crashes
>>> before that.
>>>
>>> There are around 15 connections to PostgreSQL when it crashes but most
>>> are idle
>>> there may be a few inserts but no bulk inserts, the biggest load would
>>> come from
>>> select statements.
>>>
>>
>> We haven't identified that the failed read/write are caused by anti-virus
>> software or intensive read/write. If you can compile the source, can you
>> patch smgrread()/smgrwrite() like this to capture the native windows
>> error:
>>
>> void
>> smgrwrite(SMgrRelation reln, BlockNumber blocknum, char *buffer, bool
>> isTemp)
>> {
>> if (!(*(smgrsw[reln->smgr_which].smgr_write)) (reln, blocknum, buffer,
>> isTemp))
>> ereport(ERROR,
>> (errcode_for_file_access(),
>> errmsg("could not write block %u of relation %u/%u/%u:%d: %m",
>> blocknum,
>> reln->smgr_rnode.spcNode,
>> reln->smgr_rnode.dbNode,
>> reln->smgr_rnode.relNode,
>> GetLastError())));
>> }
>>
>> Regards,
>> Qingqing
>>
>>
>> ---------------------------(end of broadcast)---------------------------
>> TIP 5: don't forget to increase your free space map settings
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster