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.

Jean-Pierre Pelletier

----- Original Message ----- From: "Qingqing Zhou" <[EMAIL PROTECTED]>
To: <pgsql-bugs@postgresql.org>
Sent: Wednesday, October 05, 2005 3:03 AM
Subject: Re: [BUGS] Possibly corrupted shared memory, PostgreSQL 8.1 beta2, Windows 2000



""Jean-Pierre Pelletier"" <[EMAIL PROTECTED]> wrote

I've installed PostgreSQL 8.1 beta2 five days ago and it crashed 3 times since then.
Here is what's been logged for the last crash

2005-10-04 11:00:19 FATAL: could not read block 121 of relation 1663/16384/2608: Invalid argument

relation 2608 is pg_depend
----------------------------------------------------------------------------------
The crash before that was on relation pg_type, the first line logged was:
2005-10-03 10:51:06 FATAL: could not read block 38 of relation 1663/16384/1247: Invalid argument
----------------------------------------------------------------------------------
The first crash was also on relation pg_depend, but with open instead or read 2005-09-30 18:38:53 FATAL: could not open relation 1663/16384/2608: Invalid argument
----------------------------------------------------------------------------------


This problem was reported several times before, but not necessarily system tables. Is there any anti-virus softwares installed on the same machine? Is the database under intensive IO pressure?

Regards,
Qingqing


---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

http://archives.postgresql.org


---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

              http://www.postgresql.org/docs/faq

Reply via email to