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

Re: fsync and semctl errors with 8.1.5/win32

From: "Jeremy Haile" <jhaile(at)fastmail(dot)fm>
To: "Jeremy Haile" <jhaile(at)fastmail(dot)fm>, "Dave Page" <dpage(at)postgresql(dot)org>
Cc: "Magnus Hagander" <mha(at)sollentuna(dot)net>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: fsync and semctl errors with 8.1.5/win32
Date: 2006-11-28 21:18:56
Message-ID: 1164748736.8620.277882623@webmail.messagingengine.com (view raw or flat)
Thread:
Lists: pgsql-bugs
OK - after uninstalling the virus scanner (McAfee), I still get the same
disk access errors.

Here's a few seconds of the log output (this has been going on for 10
mins as of this e-mail being sent):
2006-11-28 16:16:10 LOG:  could not fsync segment 0 of relation
1663/16404/30267: Permission denied
2006-11-28 16:16:10 ERROR:  storage sync failed on magnetic disk:
Permission denied
2006-11-28 16:16:11 LOG:  could not fsync segment 0 of relation
1663/16404/30267: Permission denied
2006-11-28 16:16:11 ERROR:  storage sync failed on magnetic disk:
Permission denied
2006-11-28 16:16:12 LOG:  could not fsync segment 0 of relation
1663/16404/30267: Permission denied
2006-11-28 16:16:12 ERROR:  storage sync failed on magnetic disk:
Permission denied
2006-11-28 16:16:13 LOG:  could not fsync segment 0 of relation
1663/16404/30267: Permission denied
2006-11-28 16:16:13 ERROR:  storage sync failed on magnetic disk:
Permission denied


Here's the FileMon output from the same seconds:
4:16:10 PM      postgres.exe:3168       OPEN    C:\Program
Files\PostgreSQL\8.1\data\base\16404\30267   DELETE PEND     Options:
Open  Access: 0012019F 
4:16:11 PM      postgres.exe:3168       OPEN    C:\Program
Files\PostgreSQL\8.1\data\base\16404\30267   DELETE PEND     Options:
Open  Access: 0012019F 
4:16:12 PM      postgres.exe:3168       OPEN    C:\Program
Files\PostgreSQL\8.1\data\base\16404\30267   DELETE PEND     Options:
Open  Access: 0012019F 
4:16:13 PM      postgres.exe:3168       OPEN    C:\Program
Files\PostgreSQL\8.1\data\base\16404\30267   DELETE PEND     Options:
Open  Access: 0012019F 


This is an incredibly bad problem for me.  I'd really appreciate any
help!

Jeremy


On Mon, 27 Nov 2006 12:14:00 -0500, "Jeremy Haile" <jhaile(at)fastmail(dot)fm>
said:
> Thanks for the feedback.  If you don't mind, what version of PostgreSQL
> are you running?
> 
> I'm trying to bring PostgreSQL into this company - they are primarily a
> Windows/SQL Server shop (although Java software development)  I've
> already gotten comments similar to "Why don't you just switch to SQL
> Server?" -  so I'm hoping to find a workaround before I get forced to
> switch DB platforms.  As it is, my application seems unreliable because
> I haven't been able to resolve the PostgreSQL hanging problems in
> Windows.  If I had my way, I'd switch the server to Linux - but alas,
> that hasn't been an option so far.
> 
> I know this may be the wrong list to ask this question on - but as I'm
> an outspoken PostgreSQL advocate, I'd like your opinions.  If I am
> unable to resolve these PostgreSQL issues given my constraints, will I
> likely have less problems running MySQL/InnoDB on Windows? (since it has
> had a native Windows build for much longer)
> 
> 
> On Mon, 27 Nov 2006 16:40:57 +0000, "Dave Page" <dpage(at)postgresql(dot)org>
> said:
> > Jeremy Haile wrote:
> > > I've gotten pushback from my organization on removing antivirus from the
> > > servers completely.  Are there any antiviruses that are known to be
> > > compatible with PostgreSQL/win32?  
> > 
> > All my boxes (2 build farm members, 1 production server, and the laptop 
> > on which the official releases are built and tested) run Sophos Anti 
> > Virus (http://www.sophos.com/products/es/endpoint/sav.html), with no 
> > problems.
> > 
> > Regards, Dave
> > 
> > ---------------------------(end of broadcast)---------------------------
> > TIP 6: explain analyze is your friend
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 5: don't forget to increase your free space map settings

In response to

Responses

pgsql-bugs by date

Next:From: Jeremy HaileDate: 2006-11-28 21:23:42
Subject: Re: fsync and semctl errors with 8.1.5/win32
Previous:From: Jeremy HaileDate: 2006-11-28 17:22:09
Subject: could not rename temporary statistics file: No such file or directory

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