Re: BUG #5278: Postgres hangs / crashes every day - Mailing list pgsql-bugs

Tom and Kevin,

=20

Thank you for your quick reply.

=20

I am not allowed to uninstall anti virus software on this system but can co=
nfigure the required exclusions. Anti Virus software being used is Symantec.

=20

Do any of the problems I am facing are fixed in a recent release so that I =
can upgrade to that release?

=20

Yesterday night while I was working on this system, I discovered that a Win=
dows Junction Point was configured. Are there any known issues when a windo=
ws junction point is configured to the Postgres folder?

=20

Thanks,

Murali


> To: nmmreddy11@hotmail.com
> CC: pgsql-bugs@postgresql.org
> Subject: Re: [BUGS] BUG #5278: Postgres hangs / crashes every day=20
> Date: Thu, 14 Jan 2010 18:11:24 -0500
> From: tgl@sss.pgh.pa.us
>=20
> "Murali" <nmmreddy11@hotmail.com> writes:
> > Postgres hangs / crashes every day (gets corrupted?). It neither serves=
 any
> > requests from connected applications nor accepts new connections. I can=
=92t
> > connect to the data base through PG Admin also. Below given is the log
> > snippet at the time of failure.
>=20
> > Log Snippet1:
> > 2009-12-16 10:59:11 FATAL: could not open relation 17253/33902/16729: No
> > such file or directory
>=20
> > Log Snippet2:
> > 2009-12-16 09:44:50 ERROR: could not open relation 17253/33902/16691:
> > Permission denied
>=20
> Given that last, I'd bet that most of your problems come from broken
> antivirus software. Remove it. Do not trust that excluding PG's data
> folder is sufficient. In fact, don't trust that turning the AV code off
> is sufficient. Uninstall it.
>=20
> There's some information about AV compatibility here:
> http://wiki.postgresql.org/wiki/Running_%26_Installing_PostgreSQL_On_Nati=
ve_Windows#What_Anti-Virus_software_is_compatible.3F
> but unexpected permissions errors are a smoking gun that should trump
> anything at all anyone may claim about particular AV code being okay.
>=20
> It's fairly likely that the AV code's interference has created
> corruption in your database, if Postgres was able to write some files
> but was prevented from making other parts of the same logical update.
> Once you're rid of the unexpected permissions errors, a dump and reload
> would be a good idea to try to get back to a clean state.
>=20
> The other thing you ought to consider is moving onto a supported version
> of Postgres. 8.0.6 is very old and has got numerous known bugs,
> particularly when running on Windows. You need at least
> 8.2.something-recent.
>=20
> regards, tom lane
>=20
> --=20
> Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-bugs

=20=09=09=20=09=20=20=20=09=09=20=20
_________________________________________________________________
New Windows 7: Find the right PC for you. Learn more.
http://windows.microsoft.com/shop=