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

Re: BUG #2712: could not fsync segment: Permission

From: "Thomas H(dot)" <me(at)alternize(dot)com>
To: <pgsql-bugs(at)postgresql(dot)org>
Cc: "Magnus Hagander" <mha(at)sollentuna(dot)net>,"Bruce Momjian" <bruce(at)momjian(dot)us>,"Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: BUG #2712: could not fsync segment: Permission
Date: 2006-10-27 14:30:57
Message-ID: 0ab701c6f9d4$850a1010$6501a8c0@iwing (view raw or flat)
Thread:
Lists: pgsql-bugspgsql-patches
> It might be interesting to think about not requiring the ControlFileLock
> to be held while making new WAL segments.  I think the only reason it
> does that is to ensure that link/rename failure can be treated as a hard
> error (because no one could have beat us to the filename), but we're
> already having to back off that stance for Windows ...

on a sidenote, i was able to work around the total xlog-lock by ingreasing 
checkpoint_segments from 3 (default) to 12. that seems enough to have the 
processes release (timeout?) the filehandles before writer-process wants to 
rename the xlog file, at least under normal workload. if there is a data 
load, the lockup still happens, but i can live with that for now.

the logs are still being swamped with the other delete error messages, tho:

2006-10-27 16:16:58 [5828] ERROR:  XX000: storage sync failed on magnetic 
disk: Permission denied
2006-10-27 16:16:58 [5828] LOCATION:  smgrsync, smgr.c:888
2006-10-27 16:16:59 [5828] LOG:  42501: could not fsync segment 0 of 
relation 1663/3964774/6495380: Permission denied
2006-10-27 16:16:59 [5828] LOCATION:  mdsync, md.c:785
2006-10-27 16:16:59 [5828] ERROR:  XX000: storage sync failed on magnetic 
disk: Permission denied
2006-10-27 16:16:59 [5828] LOCATION:  smgrsync, smgr.c:888

magnus, where you able to do a debug build for me to test the patch? would 
be nice if a solution could be found for the final 8.2 release.

cheers,
thomas 



In response to

pgsql-bugs by date

Next:From: Tom LaneDate: 2006-10-27 16:53:52
Subject: Re: BUG #2724: Could not check connection status with "ssl=on"
Previous:From: Alexey ZayatsDate: 2006-10-27 07:41:05
Subject: BUG #2724: Could not check connection status with "ssl=on"

pgsql-patches by date

Next:From: Neil ConwayDate: 2006-10-27 14:56:43
Subject: Re: GUC description cleanup
Previous:From: Peter EisentrautDate: 2006-10-27 13:59:45
Subject: Re: GUC description cleanup

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